Doc:latest/evalguide/csa103 - Revision history

Prasad: /* Putting it all Together */

2014-11-11T08:55:14Z

‎Putting it all Together

Prasad: /* Putting it all Together */

2014-11-11T08:52:01Z

‎Putting it all Together

Prasad: /* Initialization */

2014-11-11T08:40:31Z

‎Initialization

Prasad: /* Writing */

2014-11-11T08:39:27Z

‎Writing

Prasad: /* Reading */

2014-11-11T08:38:15Z

‎Reading

Stone: /* Putting it all Together */

2013-01-23T16:40:50Z

‎Putting it all Together

Stone: /* Summary and References */

2013-01-15T21:16:54Z

‎Summary and References

Stone: /* Additional Tests for Runtime Hardware Setup 1.3 and 2.3 */

2013-01-15T21:14:25Z

‎Additional Tests for Runtime Hardware Setup 1.3 and 2.3

Stone: /* How to Run csa103 and What to Observe */

2013-01-15T21:07:36Z

‎How to Run csa103 and What to Observe

Show changes

Stone: /* What Will You Learn */

2013-01-15T21:06:59Z

‎What Will You Learn

@@ Line 285: / Line 285: @@
 {| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
-  ! style="color:black;background-color:#ffccaa;" align="center"| clCompAppMain.c
+  ! style="color:black;background-color:#ffccaa;" align="center"| main.c
   |-
   |<code><pre>
@@ Line 321: / Line 321: @@
 {| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
-  ! style="color:black;background-color:#ffccaa;" align="center"| clCompAppMain.c
+  ! style="color:black;background-color:#ffccaa;" align="center"| main.c
   |-
   |<code><pre>
@@ Line 344: / Line 344: @@
 {| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
-  ! style="color:black;background-color:#ffccaa;" align="center"| clCompAppMain.c
+  ! style="color:black;background-color:#ffccaa;" align="center"| main.c
   |-
   |<code><pre>
@@ Line 398: / Line 398: @@
 {| cellspacing="0" cellpadding = "0" border="0" align = "center" width="680"
-  ! style="color:black;background-color:#ffccaa;" align="center"| clCompAppMain.c
+  ! style="color:black;background-color:#ffccaa;" align="center"| main.c
   |-
   |<code><pre>

@@ Line 290: / Line 290: @@
 void* csa103CkptActive(ClPtrT unused)
+{
-     ClRcT rc = CL_OK;
+     ClRcT rc = SA_AIS_OK;
      /* This thread will only be started when the application becomes active */

@@ Line 67: / Line 67: @@
 SaAisErrorT checkpoint_initialize(void)
+{
-     SaAisErrorT      rc = CL_OK;
+     SaAisErrorT      rc = SA_AIS_OK;
      SaVersionT ckpt_version = {'B', 1, 1};
      SaCkptCallbacksT callbacks;
@@ Line 105: / Line 105: @@
 SaAisErrorT checkpoint_initialize(void)
+{
-     SaAisErrorT      rc = CL_OK;
+     SaAisErrorT      rc = SA_AIS_OK;
      SaNameT    ckpt_name = { strlen(CKPT_NAME), CKPT_NAME };
      SaCkptCheckpointCreationAttributesT attrs;
@@ Line 145: / Line 145: @@
 Next, the saCkptCheckpointOpen function is called to open or create the checkpoint table.  As the processes that constitute a redundant application start, their initialization routines are racing each other to create/open the table first.  Therefore it is necessary to specify the SA_CKPT_CHECKPOINT_CREATE (in all processes) to ensure that whichever process wins will create the checkpoint.
 ====Writing====

@@ Line 163: / Line 163: @@
          clprintf(CL_LOG_SEV_ERROR, "checkpoint_replica_activate failed [0x%x] in ActiveReplicaSet", rc);
+     }
-     else rc = CL_OK;
+     else rc = SA_AIS_OK;
      return rc;

@@ Line 250: / Line 250: @@
 ClRcT checkpoint_read_seq(ClUint32T *seq)
+{
-     SaAisErrorT rc = CL_OK;
+     SaAisErrorT rc = SA_AIS_OK;
      ClUint32T err_idx; /* Error index in ioVector */
      ClUint32T seq_no = 0xffffffff;
@@ Line 265: / Line 265: @@
+     {
          if (rc != SA_AIS_ERR_NOT_EXIST)  /* NOT_EXIST is ok, just means no active has written */
-             return CL_OK;
+             return SA_AIS_OK;
          clprintf(CL_LOG_SEV_ERROR,"Error: [0x%x] from checkpoint read, err_idx = %u", rc, err_idx);
@@ Line 272: / Line 272: @@
      *seq = ntohl(seq_no);
-     return CL_OK;
+     return SA_AIS_OK;
+}
    </pre></code>
@@ Line 278: / Line 278: @@
 It is important to handle the case of a missing section properly.  Whether your application sees this error depends on the design of the application, but is a common design to see missing sections on application start because no prior "active" existed to fill the checkpoint.  In this design, it is only on failover that the sections will have been written.
 ====Putting it all Together====

@@ Line 342: / Line 342: @@
 |}
+<div id="dispatch_loop">
 Next, we enter the dispatch loop.  The auto-generated code creates a loop that handles the AMF processing.  This generated loop has been extended to also handle checkpoint processing.  Note that it is also perfectly acceptable (even easier) to spawn 2 threads and have one handle the AMF dispatches and the other checkpoint dispatches.  This code has been implemented in this manner to show how it can all be done in a single thread.
@@ Line 394: / Line 394: @@
    </pre></code>
 |}
+</div>
 Finally, when this application becomes active, we need to kick off the csa103CkptActive function in a new thread:

@@ Line 606: / Line 606: @@
 We've seen :
-*how to use Clovis' checkpoint service to save some program state and recover that state from a separate process
+*how to use the OpenClovis SAFplus checkpoint service to save some program state and recover that state from a separate process
 *how to initialize the client checkpoint library
 *how to create and open checkpoints
 *how to create and use sections in an opened checkpoint
 Further information can be found within the following: ''OpenClovis API Reference Guide''.

@@ Line 593: / Line 593: @@
 </ol>
-===Additional Tests for Runtime Hardware Setup 1.3 and 2.3===
+===Additional Experiments===
-Now repeat  the experiment till the stage before we kill  the active process  and follow these steps.
+* In the multi-node configuration, you can try a node failure instead of a process failure.  To do this, either run "etc/init.d/safplus stop" or power the node off.
-'''Step A'''
+* Have the active write to more than one checkpoint section.
-<ol>
-<li>Stop SAFplus Platform on SCNodeI0 using <code>/etc/init.d/asp stop</code>. Observer the logs <code>/root/asp/var/log/csa103CompI3Log.latest</code> on SCNodeI1. This will become active  and start printing the hello world logs as above.
-Note in this case active System Controller SCNode1 is still aware of PayloadNodeI0 and PayloadNodeI1.
-<li>Start looking at the logs  for <code>/root/asp/var/log/csa103CompI0Log.latest</code> in PayloadNodeI0. This will print the  standby  logs as  above.
-<li>Stop  SAFplus Platform  on PayloadNodeI0  and start observing the logs on PayloadNodeI1 in <code>/root/asp/var/log/csa103CompI1Log.latest</code> for standby.
-In this case, you can see, via the active System Controller logs that PayloadNodeI0 is not active whilst PayloadNodeI1 is.
-</ol>
-'''Step B'''  For Hardware Setup 1.3 only
+* Study and experiment with the other checkpoint modes -- collocated verses non-collocated and asynchronous verses synchronous.
-#Repeat A  with the slight exception  that the  blade running SCNodeI0  is  yanked out(<code>/etc/init.d/asp zap</code>) instead of gracefully shutting  down SAFplus Platform in step 1.
 ===Summary and References===

@@ Line 16: / Line 16: @@
 *how to write data to the checkpoint section
 *and read data from the checkpoint section.
-*how to extend the SAF event dispatch loop to handle multiple services.
+*how to extend the SAF dispatch loop to handle multiple libraries
 ===The Code===