View basic application information and modify configurations-Elasticsearch(ES)-阿里云帮助中心

This topic describes how to view an application's basic information, quota details, and network access settings. It also describes how to configure index creation and deletion policies, and the result count compatibility mode (TotalHitsAsInt).

Access application details

Log on to the Elasticsearch Serverless console and select the target region from the top menu bar.
In the left-side navigation pane, click Application management, and then click the name of your application to open its details page.

On this page, you can view the application's basic information, adjust the application quota, configure network access for the application, and configure policies for indices and the result count compatibility mode as needed.

View basic information

In the Basic Information section, you can view the application's type, version, username, password, tags, and creation time. You can also modify the application's tags and user password as needed.

Adjust the application quota

In the Billing quota section, you can modify quotas such as Fixed CU Quota and Vector Data Memory Usage Limit based on the application's actual resource consumption. You can also configure alert rules to monitor CU usage, ensuring your services run smoothly. This helps prevent service disruption from traffic throttling.

Note

The storage limit for a single application cannot be directly modified. By default, 1 CU corresponds to 50 GB of storage. To get more storage, increase the fixed CU quota. For example, 4 CU provides 200 GB of storage, and 6 CU provides 300 GB.

This section also includes settings such as the Elastic Cap and the Elastic Computing toggle. After making changes, click Save to apply them.

Configure network access

In the Application Access and Kibana Access sections, you can configure access to the application over the public or private network and configure an allowlist and the authentication method as needed.

Modify application configurations

In the Feature Enablement Configuration section, click Modify to configure the application's index creation and deletion policies and the result count compatibility mode.

Index creation and deletion policies

Automatic index creation: This setting corresponds to the auto_create_index setting. It controls whether to automatically create an index when a document is written to a non-existent index.
- Allow (default): The system creates the index based on the default template.
- Disallow: If you write a document to an index that does not exist, the system rejects the request and returns an error.
- Custom: You can customize the index Pattern name in the template, such as mysearch-*. The system will then create a corresponding index based on your configuration.
  Note
  - Pattern specifies the naming pattern. Only indexes that match the specified Pattern can be automatically created. For example, mysearch-* allows for the automatic creation of indexes whose names start with mysearch-.
  - Separate multiple Pattern values with commas (,).
Index deletion configuration: This setting corresponds to the destructive_requires_name setting. It controls whether you must specify an index name when deleting an index. This prevents accidental data loss from wildcard deletions. By default, this protection is enabled.

Result count compatibility mode (TotalHitsAsInt)

Result count compatibility mode is a client-side setting, often available in clients like the Java API Client, designed to ensure backward compatibility. It is mainly used during upgrades to support applications built for older Elasticsearch versions, such as 6.x and earlier, which prevents parsing errors from response format changes. This mode is disabled by default. When you enable it, the total hits in your search results (hits.total) are returned as an integer instead of the default { "value": ..., "relation": ... } object. Enabling this mode also adds the track_total_hits: true parameter to the request.

Track total hits

The track total hits limit is a protective setting to prevent deep result scanning. By default, Elasticsearch accurately counts only the first 10,000 results but allows users to exceed this limit using the track_total_hits: true request parameter. This option defaults to "No limit", which maintains the native Elasticsearch behavior.

You can set a hard limit here, for example, 5000. The effective threshold then follows a "minimum wins" rule:

If a requested limit is lower than this limit, the requested limit is used.
If the requested limit is higher than this limit, is set to true, or is unspecified (which defaults to 10,000 in Elasticsearch), the configured limit is enforced. Any hits beyond this limit will not be accurately counted.

For example, if you set the limit to 8888, the behavior is as follows.

In the Track total hits limit setting, select Custom and enter the limit in the input box to the right.

GET simple-ccppt250/_search
{
  "track_total_hits": 10000000
}

{
  "took": 7,
  "timed_out": false,
  "_shards": {
    "total": 6,
    "successful": 6,
    "skipped": 0,
    "failed": 0
  },
  "hits": {
    "total": {
      "value": 8888,
      "relation": "gte"
    },
    "max_score": 1,
    "hits": [...]
  }
}

For more information about track total hits, see Track Total Hits.