[BUG] BWC failure on backward compatibility test

[andy-k-improving]

What is the bug?

This is served as a follow up ticket for #3168 to gather all the progress and information related to the backward compatibility test failure on CI pipeline.

How can one reproduce the bug?
Steps to reproduce the behavior:

1. To trigger the Run backward compatibility tests

What is the expected behavior?
To have backward compatbility test passed on the main branch for Github CI-Runner.

What is your host/environment?
N/A

Do you have any screenshots?
https://github.com/opensearch-project/sql/actions/runs/12144751620/job/33864844886

Do you have any additional context?
As the test is executed against openserach-min distribution, which only Linux distribution is available (Not Mac and WIndows)
Contributor is encouraged to equipped with a Ubuntu machine or a equivalent virtual environment.

[RyanL1997]

Hi @andy-k-improving , I just took a look of the above log in https://github.com/opensearch-project/sql/actions/runs/11621890097/job/32366453716 and https://github.com/opensearch-project/sql/actions/runs/12144751620/job/33864844886. And I found that the BWC test is failing because the cluster cannot reach a stable state (cluster health does not reach "yellow" within 40 seconds):

cluster-manager not discovered or elected yet, an election requires at least 2 nodes

The cluster is unable to elect a cluster manager due to a lack of quorum or communication issues between nodes.

Right now, I'm trying to re-produce this on my own fork to see if this is a flaky issue due to the unstable connection of our github runner or if we need to extend the timeout for waiting for cluster health.

[Swiddis]

Possibly related to OpenSearch Lucene updates at opensearch-project/OpenSearch#15333, and this K-NN PR might also be relevant opensearch-project/k-NN#2195. (Copied from #3089)