TcpTransport

{"type": "server", "timestamp": "2022-10-19T23:49:25,152Z", "level": "WARN", "component": "o.e.t.TcpTransport", "cluster.name": "elasticsearch", "node.name": "elasticsearch-master-1", "message": "exception caught on transport layer [Netty4TcpChannel{localAddress=/10.12.7.39:9300, remoteAddress=/10.12.15.57:39524}], closing connection", "cluster.uuid": "uTbgs0LadfadfES4s8gpg", "node.id": "aBfUaadfaf_lo-XQ" ,
"stacktrace": ["io.netty.handler.codec.DecoderException: javax.net.ssl.SSLHandshakeException: Insufficient buffer remaining for AEAD cipher fragment (2). Needs to be more than tag size (16)",

.../...
Java.io.IOException: failed to obtain in-memory shard lock

See also

• Elasticsearch troubleshooting, Elasticsearch logs, yellow, Low disk watermark, in-memory shard lock, re-running
• Elasticsearch, installation, ELK, Elastic X-Pack, elasticsearch.yml, logs, ECK, Elasticsearch curl URLs, Elastisearch REST APIs, /_cat/, /_cluster/, /_xpack/, QueryShardException, Elasticsearch index, ELK backup and restore, elasticsearch-cli, Elasticsearch versions, ElasticSearch Snapshot Lifecycle Management (SLM), Low disk watermark, Elasticsearch storage, Elasticsearch users, Elasticsearch roles, search context, shards, Elastic Cloud, Elastic Licensing, ElasticSearch alerts, ESQL