cdr stats sync

The cdr stats sync command displays the progress of a synchronization operation that specified a progress report task name.


1  cdr stats sync?  %Connect Option  (1)?  --repeat=time?   --verbose?  --delete=task_name +  task_name
Notes:
Element Purpose Restrictions Syntax
task_name The name of the progress report task to display. Must be an existing named task. Long Identifiers
time The number of seconds between progress reports. Must be a positive integer.

The following table describes the options to the cdr stats sync command.

Long Form Short Form Meaning
--delete= -d Specifies to delete the specified named task information from the replcheck_stat and replcheck_stat_node tables.
--repeat= -r Specifies to repeat the progress report every specified interval of seconds.
--verbose -v Specifies that the consistency report shows specific values that are inconsistent instead of a summary of inconsistent rows.

Usage

Use the cdr stats sync command to display the progress of a synchronization operation (cdr sync replicate or cdr sync replicateset). You must be connected to the same server on which the cdr sync replicate or cdr sync replicateset command was run when you run the cdr stats sync command. The cdr stats sync command displays a snapshot of the progress report and an estimate of the time remaining to complete the synchronization operation. If you use the --repeat option, the progress report is displayed every specified time interval.

You can view the progress of previously run synchronization operations that have named tasks, if those progress report tasks have not been overwritten or deleted.

If you want to see the detailed progress report, include the --verbose option. The format of the verbose progress report is the same as the verbose consistency report generated by the cdr check replicate and cdr check replicateset commands.

If you want to delete a named task, use the --delete option.

Examples

The following example synchronizes a replicate named repl1, creates a task named tst, and then displays a progress report every two seconds.

cdr sync repl -r repl1 -m cdr1 -a --name=tst
cdr stats sync --repeat=2 tst

The progress report from the previous command might look like this:

	Job tst
	repl1                    Started Jan 17 16:10:59
	*********+----+----+----+----+----+----+----+----+ Remaining 0:00:08
	
	---------------------------------------------------
	Job tst
	repl1                    Started Jan 17 16:10:59
	**********************--+----+----+----+----+----+ Remaining 0:00:04
	
	---------------------------------------------------
	Job tst
	repl1                    Started Jan 17 16:10:59
	***********************************----+----+----+ Remaining 0:00:02
	
	---------------------------------------------------
	Job tst
	repl1                    Started Jan 17 16:10:59
	*************************************************+ Remaining 0:00:01
	
	---------------------------------------------------
	Job tst
	repl1                    Completed
	                         Started Jan 17 16:10:59, Elapsed Time 0:00:07

The following example synchronizes the replicate, creates a task named tst, and displays a verbose progress report every four seconds.

cdr sync repl -r repl1 -m cdr1 -a --name=tst 
cdr stats sync --repeat=4 --verbose tst

The progress report from the previous command might look like this:

	Job tst
	repl1                    Started Jan 17 16:34:42
	*******--+----+----+----+----+----+----+----+----+ Remaining 0:00:12
	
	Node                 Total     Extra   Missing  Mismatch     Child Processed
	---------------- --------- --------- --------- --------- --------- ---------
	cdr1                  9000         0         0         0         0         0
	cdr2                  9000         0         0        99         0        99
	cdr3                  9000         0         0         0         0         0
	
	---------------------------------------------------
	Job tst
	repl1                    Started Jan 17 16:34:42
	*********************************-+----+----+----+ Remaining 0:00:02
	
	Node                 Total     Extra   Missing  Mismatch     Child Processed
	---------------- --------- --------- --------- --------- --------- ---------
	cdr1                 43000         0         0         0         0         0
	cdr2                 43000         0         0        99         0        99
	cdr3                 43000         0         0         0         0         0
	
	---------------------------------------------------
	Job tst
	repl1                    Started Jan 17 16:34:42
	*************************************************+ Remaining 0:00:01
	
	Node                 Total     Extra   Missing  Mismatch     Child Processed
	---------------- --------- --------- --------- --------- --------- ---------
	cdr1                 39000         0         0         0         0        99
	cdr2                 38901         0        99        99         0        99
	cdr3                 39000         0         0         0         0         0
	
	---------------------------------------------------
	Job tst
	repl1                    Completed
	                         Started Jan 17 16:34:42, Elapsed Time 0:00:11
	
	Node                 Total     Extra   Missing  Mismatch     Child Processed
	---------------- --------- --------- --------- --------- --------- ---------
	cdr1                 64099         0         0         0         0        99
	cdr2                 64000         0        99        99         0        99
	cdr3                 64099         0         0         0         0         0
	

The following example synchronizes a replicate set named set, creates a task named tst, and displays a progress report every five seconds:

cdr sync replset -s set -m cdr1 -a -n tst
cdr stats sync -r 5 tst

The progress report from the previous command might look like this:

	Job tst
	repl3                    Started Jan 17 16:41:19
	*****----+----+----+----+----+----+----+----+----+ Remaining 0:00:16
	repl2                    Pending
	repl1                    Pending
	Estimated time remaining for job tst  0:00:52
	
	---------------------------------------------------
	Job tst
	repl3                    Started Jan 17 16:41:19
	***************************************+----+----+ Remaining 0:00:01
	repl2                    Pending
	repl1                    Pending
	Estimated time remaining for job tst  0:00:19
	
	---------------------------------------------------
	Job tst
	repl3                    Completed
	                         Started Jan 17 16:41:19, Elapsed Time 0:00:08
	repl2                    Started Jan 17 16:41:27
	*******************+----+----+----+----+----+----+ Remaining 0:00:06
	repl1                    Pending
	Estimated time remaining for job tst  0:00:13
	
	---------------------------------------------------
	Job tst
	repl3                    Completed
	                         Started Jan 17 16:41:19, Elapsed Time 0:00:08
	repl2                    Completed
	                         Started Jan 17 16:41:27, Elapsed Time 0:00:08
	repl1                    Started Jan 17 16:41:35
	----+----+----+----+----+----+----+----+----+----+ Remaining 0:01:08
	Estimated time remaining for job tst  0:01:08
	
	---------------------------------------------------
	Job tst
	repl3                    Completed
	                         Started Jan 17 16:41:19, Elapsed Time 0:00:08
	repl2                    Completed
	                         Started Jan 17 16:41:27, Elapsed Time 0:00:08
	repl1                    Started Jan 17 16:41:35
	*********************************-+----+----+----+ Remaining 0:00:02
	Estimated time remaining for job tst  0:00:02
	
	---------------------------------------------------
	Job tst
	repl3                    Completed
	                         Started Jan 17 16:41:19, Elapsed Time 0:00:08
	repl2                    Completed
	                         Started Jan 17 16:41:27, Elapsed Time 0:00:08
	repl1                    Completed
	                         Started Jan 17 16:41:35, Elapsed Time 0:00:11
	Run time for job tst  0:00:27