[this comment has no technical discussion in it]
Sorry huge miscommunication on my side when I said this:
for now, we can workaround the problem and there doesn’t seem to be any action on the Elasticsearch side.
Meant to say “doesn’t seem to be any action needed on the Elasticsearch side”. This was really poorly worded on my part and what I meant is that since we haven’t determined there is a root cause [yet] or actionable thing for Elasticsearch to do, I can’t yet file a bug for you all to even take action on.
Instead, what I originally wrote makes it sound like you all aren’t doing anything to help. I think this forum is incredibly helpful and very fast to respond. There aren’t a lot of products where devs (I assume, from this post and others) actually respond to topics seemingly every day. I realize this is not a support channel, though sometimes I treat it as such and I’m very appreciative of all the help I’ve received!