This seems like something ought to work, so I would call it a bug if the region didn't get created on 1 server. At first glance, it looks like the problem is that we distribute the region to all the servers before adding it to cluster config? Seems like we need to do distribution after​ adding the region to cluster config, to make sure that all servers get the region.
-Dan ________________________________ From: Mario Kevo <mario.k...@est.tech> Sent: Friday, October 8, 2021 5:31 AM To: dev@geode.apache.org <dev@geode.apache.org> Subject: Region is not created on one of the servers Hi geode-dev, We are using a system with a large number of servers. While starting all servers, in parallel, we create a region through gfsh. The problem is that on one of the servers region is not created. There is an example of the problem: We started the locator, and then go with starting the servers, one by one. In the meantime, we run the "create region" command through gfsh. All servers that are started before the "create region" command got information to create a region on itself, but the problem is in the server which is started after the "create region" command is started and not finished yet. After the "create region" command is finished, all other servers started after that will get that region in the cluster configuration and create it. What happened with this one server without a region? It is started after the "create region" command is started, so it will not get information to create a region on itself from the locator. Also, the cluster configuration doesn't have that information yet, so the server cannot read it from the received cluster configuration. So the question is, is it allowed to run commands in parallel? If yes, we should do some checks in the code to avoid this issue. If not, we need to write it somewhere in the documentation. BR, Mario
