Missing performance-analyzer.properties in OpenSearch 3.1.0 clean install

[davidhenar]

Steps to Reproduce

1. Start a container from the official image opensearchproject/opensearch:3.1.0.
2. Do not mount any external volumes (i.e., clean setup).
3. Observe logs at startup.

Observed Logs

[ERROR][o.o.p.c.c.PluginSettings ] Error loading config file /usr/share/opensearch/config/opensearch-performance-analyzer/performance-analyzer.properties
org.opensearch.performanceanalyzer.commons.config.ConfigFileException: java.io.FileNotFoundException: /usr/share/opensearch/config/opensearch-performance-analyzer/performance-analyzer.properties (No such file or directory)
...
Disabling plugin.

The directory /usr/share/opensearch/config/opensearch-performance-analyzer/ is not present, nor is the config file.

Expected Behavior

• A clean OpenSearch Docker image with the plugin enabled should provide a valid default performance-analyzer.properties file, or generate it on startup.
• If not required anymore due to removal of Java Security Manager, the plugin should not attempt to read it and fail.

Environment

• OpenSearch version: 3.1.0
• Image: opensearchproject/opensearch:3.1.0
• Distribution: Docker (default tar-based image)
• No custom volumes, mounted configs, or overrides
• JVM args reference the missing policy: -Djava.security.policy=/usr/share/opensearch/config/opensearch-performance-analyzer/opensearch_security.policy

Additional Notes

• The plugin was working as expected in 2.19.3 under the same conditions.
• The plugin is still listed as loaded in logs, but fails post-load.
• The failure is non-blocking, but clutters logs and may disable intended metrics functionality.

Suggested Fix

Either:

• Bundle a default performance-analyzer.properties file in the image,
• Or avoid referencing it when not present to prevent log noise and false errors.

[andrross]

Catch All Triage - 1 2