[Solved] Interact with port 9300

OpenSearch
, ,
1

Is there a way to test the port 9300 availability of the new opensearch-data pod?
Keep seeing connections timeout from other pods to new created data-pod. For troubleshooting purpose, is there a good way to test the port 9300 as other nodes do?

When using telnet, there’s no problem to connect the port 9300 from a ubuntu container to opensearch-data pod.
Docker image image: opensearchproject/opensearch:1.2.4

2

[Solved] By using securityadmin.sh works for me.

[opensearch@opensearch-cluster-data-0 tools]$ time ./securityadmin.sh -h 10.42.12.59  -icl   -nhnv   -cacert ~/config/root-ca.pem   -cert ~/config/kirk.pem   -key ~/config/kirk-key.pem
Security Admin v7
Will connect to 10.42.12.59:9300 ... done
ERR: Cannot connect to OpenSearch. Please refer to opensearch logfile for more information
Trace:
NoNodeAvailableException[None of the configured nodes are available: [{#transport#-1}{Iqxy93MgQ_aRuAJZJUT1ZA}{10.42.12.59}{10.42.12.59:9300}]]
        at org.opensearch.client.transport.TransportClientNodesService.ensureNodesAreAvailable(TransportClientNodesService.java:381)
        at org.opensearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:272)
        at org.opensearch.client.transport.TransportProxyClient.execute(TransportProxyClient.java:79)
        at org.opensearch.client.transport.TransportClient.doExecute(TransportClient.java:484)
        at org.opensearch.client.support.AbstractClient.execute(AbstractClient.java:433)
        at org.opensearch.client.support.AbstractClient.execute(AbstractClient.java:419)
        at org.opensearch.security.tools.SecurityAdmin.execute(SecurityAdmin.java:524)
        at org.opensearch.security.tools.SecurityAdmin.main(SecurityAdmin.java:157)

real    0m23.273s
user    0m6.311s
sys     0m0.439s