This is interesting. Looks like the problem is here:
[2021-01-05T20:55:03.497+00:00][13526][2490][es][DEBUG]: [ActiveJob] [Work::Engine::IndexAdder] [dc3770341d38b8b5c12598d3e4c795da64d47c86] {
"request": {
"url": "https://s.macwk.com:9200/.ent-search-engine-5ff4d14e8fec75986163b858/_mapping",
"method": "get",
"headers": {
"User-Agent": "Faraday v0.15.2",
"Authorization": "[FILTERED]",
"Content-Type": "application/json"
},
"params": null,
"body": null
},
"exception": "/es/www/wwwroot/server/enterprise-search/lib/war/app/middleware/request_logging_middleware.class:44: connect timed out (Faraday::TimeoutError)\n",
"duration": 30642.6,
"stack": [
"app/models/cluster.class:190:in `block in is_mapping_consistent?'",
...
]
}
From what I can tell, the URL is incorrect since it shouldn't include the port 9200. The other requests use https://s.macwk.com correctly.
What are you using for your elasticsearch.host setting? Can you share your enterprise-search.yml file?
I would try elasticsearch.host including the port explicitly, something like:
elasticsearch.host: https://s.macwk.com:443
The good news is this bug looks like it's already fixed (accidentally) and will be in the next release.