Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-18252

Fix the Hibernate ElasticSearch tests to work with ElasticSearch 8.8.x

XMLWordPrintable

      The Hibernate ElasticSearch tests have been failing since the upgrade to ElasticSearch 8.8.2, WFLY-18227. The PR was merged because the CI jobs did not run these tests. Likely because the agents these were run on did not contain Docker or Podman. This part is be resolved as well.

      The tests seem to have two issues, according the logs in podman:

      {"@timestamp":"2023-07-13T19:20:48.189Z", "log.level": "WARN", "message":"flood stage disk watermark [95%] exceeded on [_YO5G5S1TBOQyWsdhVHC0g][1e7864de5e35][/usr/share/elasticsearch/data] free: 14.4gb[3.7%], all indices on this node will be marked read-only", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch[1e7864de5e35][generic][T#15]","log.logger":"org.elasticsearch.cluster.routing.allocation.DiskThresholdMonitor","elasticsearch.cluster.uuid":"4X9iiMH3Si-KOX5eLjuh-g","elasticsearch.node.id":"_YO5G5S1TBOQyWsdhVHC0g","elasticsearch.node.name":"1e7864de5e35","elasticsearch.cluster.name":"docker-cluster"}
      

      This can be resolved by setting the environment variable cluster.routing.allocation.disk.threshold_enabled=false.

      Once that is set, a new error appeared:

      {"@timestamp":"2023-07-13T20:39:38.486Z", "log.level": "WARN", "message":"received plaintext http traffic on an https channel, closing connection Netty4HttpChannel{localAddress=/10.88.0.3:9200, remoteAddress=/10.88.0.3:38840}", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch[b43ffa1365e3][transport_worker][T#3]","log.logger":"org.elasticsearch.http.netty4.Netty4HttpServerTransport","elasticsearch.cluster.uuid":"fHb9pQFjTXGXmCAF0wyQNw","elasticsearch.node.id":"vLY19N8tRYiY7vbtAHMPmQ","elasticsearch.node.name":"b43ffa1365e3","elasticsearch.cluster.name":"docker-cluster"}
      

      This can be resolved by setting the environment variable xpack.security.enabled=false.

              jperkins-rhn James Perkins
              jperkins-rhn James Perkins
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: