Mario Kevo created GEODE-9718:
---------------------------------

             Summary: The region is not created on all servers if commands are 
run in parallel
                 Key: GEODE-9718
                 URL: https://issues.apache.org/jira/browse/GEODE-9718
             Project: Geode
          Issue Type: Bug
            Reporter: Mario Kevo


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.

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 problem is in changing cluster configuration whilst servers are coming 
up.

The solutions are:
 # Add to the documentation to not running commands that doing some changes on 
cluster configuration while the server is in starting phase.
 # Redesign all commands that can edit the cluster configuration to first wrote 
changes to the cluster config and then distribute the commands to all servers.



The second solution can lead to some problems. When the "create region" command 
is executed it got all servers from the view and sends all of them to start 
creating a region with parameters specified in the command.
 The region creating is started on all servers and after it is finished, it is 
added to the cluster configuration. In case there are some problems with 
creating a region(wrong parameter used or something else) it will not create a 
region on the existing servers and will not write anything in a cluster 
configuration.
 In case we decide to change order, it will write in the cluster config before 
the command is successful, and then we should have some backup to rollback 
cluster configuration. Also, this will affects all commands that do changes in 
cluster config.

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to