Treatment of Repeated Letdowns in Coordinated Consistent Recovery Line Compilation for Mobile Distributed Systems

Abstract

We put forward a least_int_method (least interactive method) orchestrated CRL-compilation (consistent recovery line compilation) etiquette for non- deterministic Mob_DS (Mobile Distributed Systems); where no inoperable reinstatement-points are recorded. Recurrent terminations of CRL-compilation procedure may happen in Mobile_DS due to exhausted battery, non-voluntary disconnections of Mob_Nodes, or poor wireless connectivity. Therefore, we put forward that in the first stage, all pertinent Mob_Nodes will capture transient reinstatement-point only. Transient reinstatement-point is stored on the memory of Mob_Node only. In this case, if some method fails to capture its reinstatement-point in the first stage, then Mob_Nodes need to abandon their transient reinstatement-points only. In this way, we try to abate the loss of CRL-compilation effort when any method fails to capture its reinstatement-point in harmonization with others. We also try to reduce the CRL- compilation time and intrusion time of methods by limiting CRL-compilation tree which may be formed in other etiquettes [2, 9, 10]. We captured the transitive dependencies during the normal execution by piggybacking causal-dependency-vectors onto computation communications.