Major Description
Currently BSP Peer initializes itself to start a task afresh from superstep -1. We should have a new flavor of BSP Peer that would be started by GroomServer to recover a task as directed by BSP Master. The BSP Peer should start the task knowing the superstep number to start with, the task ID, the attemptID and the partition of the checkpointed file. The input would not be split in this case. The BSP Peer should update its task status at Groomserver as RUNNING once the task is out of the recovery superstep barrier sync.