In cli mode of docker container, set autodetectCluster=true to cause read access timeout

[siyecoo]

In cli mode of docker container, set autodetectCluster=true to cause read access timeout
go

The method here performs the IP address read into the container, resulting in a timeout that occurs when the container is deployed

[siyecoo]

[yii-bot]

Thanks for posting in our issue tracker.
In order to properly assist you, we need additional information:

• When does the issue occur?
• What do you see?
• What was the expected result?
• Can you supply us with a stacktrace? (optional)
• Do you have exact code to reproduce it? Maybe a PHPUnit tests that fails? (optional)

Thanks!

This is an automated comment, triggered by adding the label status:need more info.

[samdark]

Sounds like a very specific environment is needed to reproduce it. Would you please provide a bit more details on the problem so this specifity isn't required? Maybe a unit test?

[siyecoo]

I can give an example of my application scenario

My Yii project is deployed in the docker container, and elasticsearch is also deployed in one container. The two containers are under the same network. When I configure components, the configured node node is 127.0.0.1:9200 (ports have been mapped between the host and the container). In the PHP FPM scenario, when I execute model:: findone ($ID), there is no problem with the data, When the problem occurs in cli mode, I know through breakpoint printing that the problem is that when the variable autodetectcluster is set to true, the code executes to the file yiisoft / yii2-elasticsearch / connection In the open() method under PHP, $this - > populatenodes(), this method will trigger $response = $this - > httprequest ('Get ', "$protocol: / / $host / _nodes / _all / HTTP"); As a result, the node node will be u 。
Please look at my screenshot above

[samdark]

So there is a timeout during container deployed? How should it behave in this case?

[schmunk42]

When the problem occurs in cli mode

How do you run cli mode? Via docker exec or docker run - should be exec, otherwise you'll spin up a new container which might cause issues.