You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@geode.apache.org by "balesh2 (GitHub)" <gi...@apache.org> on 2018/12/04 18:56:39 UTC

[GitHub] [geode] balesh2 commented on issue #2933: GEODE-6107: in test start locators one at a time

@onichols-pivotal It is documented here: https://geode.apache.org/docs/guide/10/configuring/running/running_the_locator.html
Here is what the docs have to say:
"When starting up multiple locators, do not start them up in parallel (in other words, simultaneously). As a best practice, you should wait approximately 30 seconds for the first locator to complete startup before starting any other locators. To check the successful startup of a locator, check for locator log files. To view the uptime of a running locator, you can use the gfsh status locator command."

This is a bug that will only affect certain ways of starting servers and locators. Those would be if the user created a script that intentionally started locators in parallel or through the api. This also affects PCC, but they have handled that case and are aware of the issue.

I think our tests are the most affected by this. I introduced a new method to wait for the locator to start, and we may want to consider making that part of the ClusterStartupRule's startLocator() so that we always wait for the member to be done starting up. For now, I think introduction of the new method will be sufficient.

[ Full content available at: https://github.com/apache/geode/pull/2933 ]
This message was relayed via gitbox.apache.org for notifications@geode.apache.org