Current distributed deployment script forces #grapher to be a divisor of #keeper. This means the RecordingGroup size has to be the same for the entire deployment. In a more realistic system, RecordingGroup size may not be the same for all groups. Thus, the deployment script should support non-uniform RecordingGroup size.
Hosts files for different ChronoKeepers in different RecordingGroups can be generated by assigning Keeper nodes to groups in a round-robin fashion. As long as the hosts files are correct, the conf file for those Keepers can be generated accordingly. During launch, Keepers can read from the correct conf file using the group id and its hostname.
Current distributed deployment script forces #grapher to be a divisor of #keeper. This means the RecordingGroup size has to be the same for the entire deployment. In a more realistic system, RecordingGroup size may not be the same for all groups. Thus, the deployment script should support non-uniform RecordingGroup size. Hosts files for different ChronoKeepers in different RecordingGroups can be generated by assigning Keeper nodes to groups in a round-robin fashion. As long as the hosts files are correct, the conf file for those Keepers can be generated accordingly. During launch, Keepers can read from the correct conf file using the group id and its hostname.