Minor improvements
Troubleshooting expired certificates, settings, broken link, etc.
This commit is contained in:
parent
21ae64aac9
commit
4ffdce6377
|
@ -1,6 +1,6 @@
|
||||||
---
|
---
|
||||||
layout: default
|
layout: default
|
||||||
title: Create Dashboards
|
title: Create PerfTop Dashboards
|
||||||
parent: Performance Analyzer
|
parent: Performance Analyzer
|
||||||
nav_order: 2
|
nav_order: 2
|
||||||
---
|
---
|
||||||
|
|
|
@ -48,11 +48,11 @@ Otherwise, just specify the OpenSearch endpoint:
|
||||||
./opensearch-perf-top-macos --dashboard dashboards/<dashboard>.json --endpoint my-cluster.my-domain.com
|
./opensearch-perf-top-macos --dashboard dashboards/<dashboard>.json --endpoint my-cluster.my-domain.com
|
||||||
```
|
```
|
||||||
|
|
||||||
PerfTop has four pre-built dashboards in the `dashboards` directory, but you can also [create your own]({{site.url}}{{site.baseurl}}/dashboards/).
|
PerfTop has four pre-built dashboards in the `dashboards` directory, but you can also [create your own]({{site.url}}{{site.baseurl}}/monitoring-plugins/pa/dashboards/).
|
||||||
|
|
||||||
You can also load the pre-built dashboards (ClusterOverview, ClusterNetworkMemoryAnalysis, ClusterThreadAnalysis, or NodeAnalysis) without the JSON files, such as `--dashboard ClusterThreadAnalysis`.
|
You can also load the pre-built dashboards (ClusterOverview, ClusterNetworkMemoryAnalysis, ClusterThreadAnalysis, or NodeAnalysis) without the JSON files, such as `--dashboard ClusterThreadAnalysis`.
|
||||||
|
|
||||||
PerfTop has no interactivity. Start the application, monitor the dashboard, and press esc, q, or Ctrl + C to quit.
|
PerfTop has no interactivity. Start the application, monitor the dashboard, and press Esc, Q, or Ctrl + C to quit.
|
||||||
{: .note }
|
{: .note }
|
||||||
|
|
||||||
|
|
||||||
|
|
|
@ -65,4 +65,12 @@ PUT _cluster/settings
|
||||||
|
|
||||||
You can find `opensearch.yml` in `/usr/share/opensearch/config/opensearch.yml` (Docker) or `/etc/opensearch/opensearch.yml` (most Linux distributions) on each node.
|
You can find `opensearch.yml` in `/usr/share/opensearch/config/opensearch.yml` (Docker) or `/etc/opensearch/opensearch.yml` (most Linux distributions) on each node.
|
||||||
|
|
||||||
|
You don't mark settings in `opensearch.yml` as persistent or transient, and settings use the flat form:
|
||||||
|
|
||||||
|
```yml
|
||||||
|
cluster.name: my-application
|
||||||
|
action.auto_create_index: true
|
||||||
|
compatibility.override_main_response_version: true
|
||||||
|
```
|
||||||
|
|
||||||
The demo configuration includes a number of settings for the security plugin that you should modify before using OpenSearch for a production workload. To learn more, see [Security]({{site.url}}{{site.baseurl}}/security-plugin/).
|
The demo configuration includes a number of settings for the security plugin that you should modify before using OpenSearch for a production workload. To learn more, see [Security]({{site.url}}{{site.baseurl}}/security-plugin/).
|
||||||
|
|
|
@ -11,16 +11,32 @@ redirect_from: /troubleshoot/
|
||||||
This page contains a list of common issues and workarounds.
|
This page contains a list of common issues and workarounds.
|
||||||
|
|
||||||
|
|
||||||
## Java error during startup
|
|
||||||
|
|
||||||
You might see `[ERROR][c.a.o.s.s.t.OpenSearchSecuritySSLNettyTransport] [opensearch-node1] SSL Problem Insufficient buffer remaining for AEAD cipher fragment (2). Needs to be more than tag size (16)` when starting OpenSearch. This problem is a [known issue with Java](https://bugs.openjdk.java.net/browse/JDK-8221218) and doesn't affect the operation of the cluster.
|
|
||||||
|
|
||||||
|
|
||||||
## OpenSearch Dashboards fails to start
|
## OpenSearch Dashboards fails to start
|
||||||
|
|
||||||
If you encounter the error `FATAL Error: Request Timeout after 30000ms` during startup, try running OpenSearch Dashboards on a more powerful machine. We recommend four CPU cores and 8 GB of RAM.
|
If you encounter the error `FATAL Error: Request Timeout after 30000ms` during startup, try running OpenSearch Dashboards on a more powerful machine. We recommend four CPU cores and 8 GB of RAM.
|
||||||
|
|
||||||
|
|
||||||
|
## Multi-tenancy issues in OpenSearch Dashboards
|
||||||
|
|
||||||
|
If you're testing multiple users in OpenSearch Dashboards and encounter unexpected changes in tenant, use Google Chrome in an Incognito window or Firefox in a Private window.
|
||||||
|
|
||||||
|
|
||||||
|
## Expired certificates
|
||||||
|
|
||||||
|
If your certificates have expired, you might receive the following error or something similar:
|
||||||
|
|
||||||
|
```
|
||||||
|
ERROR org.opensearch.security.ssl.transport.SecuritySSLNettyTransport - Exception during establishing a SSL connection: javax.net.ssl.SSLHandshakeException: PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
|
||||||
|
Caused by: java.security.cert.CertificateExpiredException: NotAfter: Thu Sep 16 11:27:55 PDT 2021
|
||||||
|
```
|
||||||
|
|
||||||
|
To check the expiration date for a certificate, run this command:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
openssl x509 -enddate -noout -in <certificate>
|
||||||
|
```
|
||||||
|
|
||||||
|
|
||||||
## Encryption at rest
|
## Encryption at rest
|
||||||
|
|
||||||
The operating system for each OpenSearch node handles encryption of data at rest. To enable encryption at rest in most Linux distributions, use the `cryptsetup` command:
|
The operating system for each OpenSearch node handles encryption of data at rest. To enable encryption at rest in most Linux distributions, use the `cryptsetup` command:
|
||||||
|
@ -85,8 +101,3 @@ The security plugin blocks the update by script operation (`POST <index>/_update
|
||||||
## Illegal reflective access operation in logs
|
## Illegal reflective access operation in logs
|
||||||
|
|
||||||
This is a known issue with Performance Analyzer that shouldn't affect functionality.
|
This is a known issue with Performance Analyzer that shouldn't affect functionality.
|
||||||
|
|
||||||
|
|
||||||
## Multi-tenancy issues in OpenSearch Dashboards
|
|
||||||
|
|
||||||
If you're testing multiple users in OpenSearch Dashboards and encounter unexpected changes in tenant, use Google Chrome in an Incognito window or Firefox in a Private window.
|
|
||||||
|
|
Loading…
Reference in New Issue