Replication Manager

Instruction:

1. tar zxvf repman.tar.gz
   A new directory ./replication will be created where all the scripts, library and class files are stored.
    
2. Modify the configuration file repman.conf.
   In most cases the only part you need to change is the JBoss server information:
   Specify the "hostname:port" of each JBoss server and the path to the JBoss home directory on each server as well.
   (Note: Currently the replication manager has to be able to SSH to all the JBoss server machines without extra user authentication, e.g. machines in the Game cluster.)
   
   You can also control whether to start the Fault-Injector and/or the Client with the Replication Manager, and some of their runtime parameters in repman.conf.
    
3. To run the Replication Manager: .../replication/repman >& repman_log &
   Repman will run in background, starting all the JBoss servers you specified in repman.conf, and all the other components (i.e., HealthCheckerDaemon class, Fault-Injector/Client if enabled in repman.conf); then it will keep monitoring all the server replicas.
    
4. Log files:
   The following log files (as long as other tmp files) will be generated by multiple scripts in the same directory with repman:
   • log
     The log of fault injection/detection/recovery time by faultinjector and repman.
   • serverlog.txt / clientlog.txt
     The log of the time difference between two consecutive messages received by the Client.
   • repman_log / client_log / fi_log
     The standard output of repman / Client / faultinjector including all the possible error messages.
   
   You can find the logs of all the test runs we have done so far here.