PowerProtect：Data Manager ESDB — 数据过大，数据用于活动

Summary: 由于 Elasticsearch 数据库的文档增加，PowerProtect Data Manager 活动停止。 发现的错误包括：数据太大，[_id]的数据将为[859222328/819.4mb]，大于[858993459/819.1mb]的限制”

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

PowerProtect Data Manager 活动，例如：备份、还原或复制进程会因 Elasticsearch 问题而受到影响。

  • Elasticsearch index_activity索引中显示以下错误：

                    "reason": Object {
                    "caused_by": Object {
                        "caused_by": Object {
                            "bytes_limit": Number(858993459),
                            "bytes_wanted": Number(859222328),
                            "durability": String("PERMANENT"),
                            "reason": String("[fielddata] Data too large, data for [_id] would be [859222328/819.4mb], which is larger than the limit of [858993459/819.1mb]"),
                            "type": String("circuit_breaking_exception"),
                        },
                        "reason": String("CircuitBreakingException[[fielddata] Data too large, data for [_id] would be [859222328/819.4mb], which is larger than the limit of [858993459/819.1mb]]"),
                        "type": String("execution_exception"),
                    },
                    "reason": String("java.util.concurrent.ExecutionException: CircuitBreakingException[[fielddata] Data too large, data for [_id] would be [859222328/819.4mb], which is larger than the limit of [858993459/819.1mb]]"),
                    "type": String("exception"),
                },
                "shard": Number(0),
            },

  • Elasticsearch 日志指示以下内容：

    org.elasticsearch.transport.RemoteTransportException: [local][127.0.0.1:14400][indices:data/read/search[phase/query]]
Caused by: org.elasticsearch.search.query.QueryPhaseExecutionException: Query Failed [Failed to execute main query]
        at org.elasticsearch.search.query.QueryPhase.executeInternal(QueryPhase.java:228) ~[elasticsearch-7.17.17.jar:7.17.17]
        at org.elasticsearch.search.query.QueryPhase.execute(QueryPhase.java:98) ~[elasticsearch-7.17.17.jar:7.17.17]
        at org.elasticsearch.search.SearchService.loadOrExecuteQueryPhase(SearchService.java:459) ~[elasticsearch-7.17.17.jar:7.17.17]
        at org.elasticsearch.search.SearchService.executeQueryPhase(SearchService.java:623) ~[elasticsearch-7.17.17.jar:7.17.17]
        at org.elasticsearch.search.SearchService.lambda$executeQueryPhase$2(SearchService.java:484) ~[elasticsearch-7.17.17.jar:7.17.17]
        at org.elasticsearch.action.ActionRunnable.lambda$supply$0(ActionRunnable.java:47) [elasticsearch-7.17.17.jar:7.17.17]
        at org.elasticsearch.action.ActionRunnable$2.doRun(ActionRunnable.java:62) ~[elasticsearch-7.17.17.jar:7.17.17]
        at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:26) [elasticsearch-7.17.17.jar:7.17.17]

  • 发现index_activity indice 的 Elasticsearch 大小为 21.6 GB

    ┌─────┬────────┬────────┬───────────────────────────┬────────────────────────┬─────┬─────┬────────────┬──────────────┬────────────┬────────────────┐
│ ##  ┆ health ┆ status ┆ index                     ┆ uuid                   ┆ pri ┆ rep ┆ docs.count ┆ docs.deleted ┆ store.size ┆ pri.store.size │
╞═════╪════════╪════════╪═══════════════════════════╪════════════════════════╪═════╪═════╪════════════╪══════════════╪════════════╪════════════════╡
│ 1   ┆ green  ┆ open   ┆ index_activity            ┆ VCi1Df7tQLemZrSnYLyHZg ┆ 1   ┆ 0   ┆ 87971760   ┆ 8576108      ┆ 21.6gb     ┆ 21.6gb         │
│ 2   ┆ green  ┆ open   ┆ index_protection_copy_set ┆ NzMVnlX_RPG0v3dUXXGznA ┆ 1   ┆ 0   ┆ 15634865   ┆ 4026853      ┆ 6gb        ┆ 6gb            │
│ 3   ┆ green  ┆ open   ┆ index_asset_protection_de ┆ nujLQyzmRTuCsDlR5ncvBw ┆ 1   ┆ 0   ┆ 6131465    ┆ 1282123      ┆ 3.4gb      ┆ 3.4gb          │
│     ┆        ┆        ┆ tail                      ┆                        ┆     ┆     ┆            ┆              ┆            ┆                │
│ 4   ┆ green  ┆ open   ┆ index_protection_copy     ┆ JPGjWiwUS0Wilw87QWE_OA ┆ 1   ┆ 0   ┆ 2542590    ┆ 277569       ┆ 2.1gb      ┆ 2.1gb          │

  • 我们观察到 ESDB 进程利用率很高，CPU 峰值高达 900%

 

Cause

发现 Elasticsearch index_activity索引存在问题。
在估计字段加载到 JVM 堆中所需的内存量时，节点会过载。它会在操作堆超过限制时引发异常，从而阻止字段数据加载。

 

Resolution

减小了 ESDB：index_activity 索引的容量大小，以从表中删除过时的文档，从而提高了 ESDB 的整体性能。
由于这是一项内部任务，请勿 考虑自行进行任何更改！
此活动需要关注支持人员，请向戴尔团队提出服务请求。

 

Article Properties
Article Number: 000227476
Article Type: Solution
Last Modified: 02 Sept 2025
Version:  2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.