6.2.3 Monitoring Director Operation Information

Interstage Shunsaku Data Manager Operator's Guide - Microsoft(R) Windows(R) 2000/ Microsoft(R) Windows Server(TM) 2003 - - UNIX -

Contents Index

Chapter 6 Monitoring and Logging

> 6.2 Monitoring Operation Information

6.2.3 Monitoring Director Operation Information

Director operation information can be used for the following purposes:

Checking the operating status of directors
Checking director data information (the amount of data, fragmentation, backup status)
Checking the storage number and the file size of directors
Checking whether there are any errors with any searchers connected to the director
Checking whether there are any imbalances in the amounts of data allocated to searchers connected to the director.

The director operation information can be obtained by executing shundstate command.

Example 1

The following example shows how director operation information is displayed.

shundstate -s shund1 -w 
Shunsaku shundstate 2006/01/01 19:01:00

(1)      (2)                  (3)                  (4)                  (5)
Time     State                DataFileStatus       DataSize             Fragments(%)
         (6)                  (7)                  (8) 
         LastBackedUp         OperationLogStatus   OperationLogSize   
         (9)                  (10)                 (11)                 (12) 
         Records              ReadRecords          ReadTime(sec)        ReadSize 

19:01:00 ACTIVE               NORMAL               40.0GB               2
         2006/01/01 12:00:00  NORMAL               10.0KB 
         100000               12000                5.020                2.00MB

The following table shows the explanation of the item displayed.

Item Displayed

Explanation

(1) Time

Output time (hh:mm:ss)

(2) State

The operating status of the director
The operating status of the director is displayed as follows:

ACTIVE: Running
ACTIVATING: Starting up
DEGRADED: Degraded
DEGRADING: Degrading
RESENDING: Reallocating data
SWITCHING: Switching to the alternative searcher, or switching to the alternative searcher due to the searcher error and the failover.
CONDENSING: Optimizing data
BACKUP: Backing up data
RECOVER: Recovering data
WAITING: Waiting for searchers to connect

(3) DataFileStatus

Status of the storage directory for director data files
The status of the storage directory for director data files is displayed as follows:

NORMAL: Normal status
WARNING: Amount of space used by the director data file reached the alarm point, or total number of records that can be searched reached the alarm point.
LIMIT: Amount of space used by the director data file reached the maximum value, or total number of records that can be searched reached the maximum value.
FULL: Insufficient space for director data files
IOERROR: I/O fault with director data files

(4) DataSize

Total amount of director data

(5) Fragments(%)

Fragmentation rate (%)

(6) LastBackedUp

Time when the most recent backup start declaration was made (YYYY/MM/DD hh:mm:ss)

(7) OperationLogStatus

Status of the storage directory for the operation log files (output only when the OperationLogFolder parameter is specified in the director environment file)
The status of the storage directory for operation log files is displayed as follows:

NORMAL: Normal status
WARNING: Amount of space used by the operation log file reached the alarm point.
LIMIT: Amount of space used by the operation log file reached the maximum value.
FULL: Insufficient space for operation log files
IOERROR: I/O fault with operation log files

(8) OperationLogSize

Amount of space used by operation log files (output only when the OperationLogFolder parameter is specified in the director environment file)

(9) Records

Total number of records that can be searched

(10) ReadRecords

Cumulative number of XML data records that have been read (displays the cumulative number of XML data records that have been read from the director data file)

(11) ReadTime(sec)

Cumulative time (in seconds) spent reading XML data (displays the cumulative amount of time spent reading XML data from the director data file)

(12) ReadSize

Cumulative size of the XML data that has been read (displays the cumulative size of the XML data that has been read from the director data file).

Item Displayed	Explanation
(1) Time	Output time (hh:mm:ss)
(2) State	The operating status of the director The operating status of the director is displayed as follows: ACTIVE: Running ACTIVATING: Starting up DEGRADED: Degraded DEGRADING: Degrading RESENDING: Reallocating data SWITCHING: Switching to the alternative searcher, or switching to the alternative searcher due to the searcher error and the failover. CONDENSING: Optimizing data BACKUP: Backing up data RECOVER: Recovering data WAITING: Waiting for searchers to connect
(3) DataFileStatus	Status of the storage directory for director data files The status of the storage directory for director data files is displayed as follows: NORMAL: Normal status WARNING: Amount of space used by the director data file reached the alarm point, or total number of records that can be searched reached the alarm point. LIMIT: Amount of space used by the director data file reached the maximum value, or total number of records that can be searched reached the maximum value. FULL: Insufficient space for director data files IOERROR: I/O fault with director data files
(4) DataSize	Total amount of director data
(5) Fragments(%)	Fragmentation rate (%)
(6) LastBackedUp	Time when the most recent backup start declaration was made (YYYY/MM/DD hh:mm:ss)
(7) OperationLogStatus	Status of the storage directory for the operation log files (output only when the OperationLogFolder parameter is specified in the director environment file) The status of the storage directory for operation log files is displayed as follows: NORMAL: Normal status WARNING: Amount of space used by the operation log file reached the alarm point. LIMIT: Amount of space used by the operation log file reached the maximum value. FULL: Insufficient space for operation log files IOERROR: I/O fault with operation log files
(8) OperationLogSize	Amount of space used by operation log files (output only when the OperationLogFolder parameter is specified in the director environment file)
(9) Records	Total number of records that can be searched
(10) ReadRecords	Cumulative number of XML data records that have been read (displays the cumulative number of XML data records that have been read from the director data file)
(11) ReadTime(sec)	Cumulative time (in seconds) spent reading XML data (displays the cumulative amount of time spent reading XML data from the director data file)
(12) ReadSize	Cumulative size of the XML data that has been read (displays the cumulative size of the XML data that has been read from the director data file).

The statistical information in items (10) to (12) can be reset by executing this command with the -r option. Information is then calculated by counting from the time that the information was reset.

Director operation information can also be collected at fixed time intervals. In this case, the following items show the increases that have occurred during the time interval.

Cumulative time (in seconds) spent reading XML data
Cumulative number of XML data records that have been read
Cumulative size of the XML data that has been read

The "WARNING" or "LIMIT" status in (3) DataFileStatus shows that the director data file or the number of records has been reached the alarm point or the maximum value. Execute the shundstate command with the -i option to check which status it is.

The status in (3) DataFileStatus may be displayed as "LIMIT" before the (9) Records exceed the maximum value of number of records that can be stored. The status becomes "LIMIT" because the total number of the number of records to be searched and the records that are being added has already reached the maximum value. Execute the shundstate command to with the -i option to check the total number of records.

Example 2

The following information is example of the director operation information.

shundstate -s shund1  -i
Shunsaku shundstate 2006/01/01 20:00:00

(1)                 (2)              (3)                     (4)
StoredRecordsStatus StoredRecords    WarningStoredRecords    MaxStoredRecords
(5)                 (6)              (7)                     (8)
DataFileStatus      DataFileSize     WarningDataFileSize     MaxDataFileSize
(9)                 (10)             (11)                    (12)
OperationLogStatus  OperationLogSize WarningOperationLogSize MaxOperationLogSize

NORMAL              200000           3500000                 4000000
NORMAL              300MB            5000MB                  10000MB
NORMAL              100MB            900MB                   1000MB

The following table shows the explanation of the item displayed.

Item Displayed

Explanation

(1) StoredRecordsStatus

The status about the number of stored records for the dirctor are displayed as follows:

NORMAL: Normal status
WARNING: Total number of records that can be searched has reached the alarm point.
LIMIT: Total number of records that can be searched and are being added has reached the maximum value.

(2) StoredRecords

Total number of record that can be searched and are being added.

(3) WarningStoredRecords

Alarm point for the number of stored records

(4) MaxStoredRecords

Maximum value for the number of stored records

(5) DataFileStatus

Status of the director data file

NORMAL: Normal status
WARNING: Amount of space used by the director data file has reached the alarm point
LIMIT: Amount of space used by the director data file has reached the maximum value.
FULL: Insufficient space for director data files
IOERROR: I/O fault with director data files

(6) DataFileSize

Amount of space used by the director data file

(7) WarningDataFileSize

Alarm point of the director data file size

(8) MaxDataFileSize

Maximum of the director data file size

(9) OperationLogStatus

Status of the operation log file

NORMAL: Normal status
WARNING: Amount of space used by the operation log file has reached the alarm point
LIMIT: Amount of space used by the operation log file has reached the maximum value.
FULL: Insufficient space for operation log files
IOERROR: I/O fault with operation log files

(10) OperationLogSize

Amount of space used by the operation log file

(11) WarningOperationLogSize

Alarm point of the operation file size

(12) MaxOperationLogSize

Maximum of the operation log file size

Item Displayed	Explanation
(1) StoredRecordsStatus	The status about the number of stored records for the dirctor are displayed as follows: NORMAL: Normal status WARNING: Total number of records that can be searched has reached the alarm point. LIMIT: Total number of records that can be searched and are being added has reached the maximum value.
(2) StoredRecords	Total number of record that can be searched and are being added.
(3) WarningStoredRecords	Alarm point for the number of stored records
(4) MaxStoredRecords	Maximum value for the number of stored records
(5) DataFileStatus	Status of the director data file NORMAL: Normal status WARNING: Amount of space used by the director data file has reached the alarm point LIMIT: Amount of space used by the director data file has reached the maximum value. FULL: Insufficient space for director data files IOERROR: I/O fault with director data files
(6) DataFileSize	Amount of space used by the director data file
(7) WarningDataFileSize	Alarm point of the director data file size
(8) MaxDataFileSize	Maximum of the director data file size
(9) OperationLogStatus	Status of the operation log file NORMAL: Normal status WARNING: Amount of space used by the operation log file has reached the alarm point LIMIT: Amount of space used by the operation log file has reached the maximum value. FULL: Insufficient space for operation log files IOERROR: I/O fault with operation log files
(10) OperationLogSize	Amount of space used by the operation log file
(11) WarningOperationLogSize	Alarm point of the operation file size
(12) MaxOperationLogSize	Maximum of the operation log file size

The displayed items (3), (4), (7), (8), (11) and (12) are the setup value of the following execution parameters in the director environment file. If the value is not specified, the hyphen (-) is displayed.
(3) WarningStoredRecords execution parameter
(4) MaxStoredRecords execution parameter
(7) WarningDataFileSize execution parameter
(8) MaxDataFileSize execution parameter
(11) WarningOperationLogSize execution parameter
(12) MaxOperationLogSize execution parameter
If the OperationLogFolder in the director environment file is not specified, the displayed items from (9) to (12) are not output.
If the status of the director data file is "IOERROR", hyphen (-) is displayed at the (7) DataFileSize.
If the status of the operation log file is "IOERROR", hyphen (-) is displayed at the (11) OperationLogSize.

Example 3

The following examples show the output of the information used for director data in CSV format.

shundstate -s shund1  -l -C > C:\shunwork\monitor\dirstate.csv

shundstate -s shund1  -l -C > /home/shunsaku/monitor/dirstate.csv

The details in dirstate.csv

"StoredRecordsStatus","StoredRecords","WarningStoredRecords","MaxStoredRecords","DataFileStatus","DataFileSize","WarningDataFileSize","MaxDataFileSize","OperationLogStatus","OperationLogSize","WarningOperationLogSize","MaxOperationLogSize"
"NORMAL",200000,3500000,4000000,"NORMAL",314572800,5242880000,10485760000,"NORMAL",104857600,943718400,1048576000

The first line of the output is the name of the item. The director operation information will be output from the second line.
The unit of the values that are output in the DataFileSize column, the WarningDataFileSize column, the MaxDataFileSize column, the OperationLogSize column , the WarningOperationLogSize column, and the MaxOperationLogSize is a byte unit.
Each record ends with a linefeed code.

CSV files are output using the following format:

Enclose character string items in double quotes (").
Do not enclose numerical values in double quotes (").

Example 4

In the following example, operation information for a director is collected three times at 60-second intervals and then displayed.

shundstate -s shund1 -w 60 3 
Shunsaku shundstate 2006/01/01 19:01:00

Time     State                DataFileStatus       DataSize             Fragments(%)
         LastBackedUp         OperationLogStatus   OperationLogSize
         Records              ReadRecords          ReadTime(sec)        ReadSize

19:02:00 ACTIVE               NORMAL               40.0GB               2
         2006/01/01 12:00:00  NORMAL               10.0KB
         100000               12000                2.080                1.42MB

19:03:00 ACTIVE               NORMAL               40.0GB               2
         2006/01/01 12:00:00  NORMAL               10.0KB
         100000               20000                7.102                3.00MB

19:04:00 ACTIVE               NORMAL               40.0GB               2
         2006/01/01 12:00:00  NORMAL               10.0KB
         100000               3130                 1.050                318KB

Example 5

In the following example, operation information for a director is collected three times at 60-second intervals and then output in CSV format.
shundstate -s shund1 -w -C 60 3 > C:\shunwork\monitor\dirstate.csv

shundstate -s shund1 -w -C 60 3 > /home/shunsaku/monitor/dirstate.csv

Content of dirstate.csv

"Time","State","DataFileStatus","DataSize","Fragments(%)","LastBackedUp","OperationLogStatus","OperationLogSize","Records","ReadRecords","ReadTime(sec)
","ReadSize"
"2006/01/01 19:02:00","ACTIVE","NORMAL",42949672960,2,"2006/01/01 12:00:00","NORMAL",10240,100000,12000,2.080,1488977
"2006/01/01 19:03:00","ACTIVE","NORMAL",42949672960,2,"2006/01/01 12:00:00","NORMAL",10240,100000,20000,7.102,3145728
"2006/01/01 19:04:00","ACTIVE","NORMAL",42949672960,2,"2006/01/01 12:00:00","NORMAL",10240,100000,3130,1.050,325632

Column headings are output in the first line, and director operation information is output from the second line.
The "Time" column uses date/time format (YYYY/MM/DD hh:mm:ss).
The values in the "DataSize", "OperationLogSize" and "ReadSize" columns are displayed in bytes.
Each record ends with a linefeed code.

CSV files are output using the following format:

Enclose character string items in double quotes (").
Do not enclose numerical values in double quotes (").

Information about searchers connected to the director can be obtained by executing the shundstate command with the -p option.

Example 6

The following example shows how information for the searchers connected to the director is displayed.

shundstate -s shund1 -p 
Shunsaku shundstate 2006/01/01 19:01:00

(1)                 (2)      (3)             (4)          (5)         (6)      (7)
Type                ID       Hostname        State        Records     DataSize LatestTime(sec)
Searcher            shuns04  SchSvr04        INACTIVE     0           0.00KB   0.000
Searcher            shuns03  SchSvr03        ACTIVE       50000       12.0MB   0.910
Searcher            shuns02  SchSvr02        ACTIVE       50000       12.0MB   0.890
Searcher            shuns01  SchSvr01        ACTIVE       50000       12.0MB   0.900
AlternativeSearcher shuns05  SchWSvr01       ACTIVE       50000       12.0MB   0.900

The following table shows the explanation of the item displayed.

Item Displayed

Explanation

(1) Type

Process type
One of the following is displayed for the process type:

Searcher
AlternativeSearcher

(2) ID

Searcher identifier

(3) Hostname

Host name or IP address of the searcher

(4) State

Operating status of the searcher
The operating status of the searcher is displayed as follows:

ACTIVE: Running
ACTIVATING: Starting up
INACTIVE: Stopped

(5) Records

Number of records that can be searched

(6) DataSize

Amount of data that can be searched

(7) LatestTime(sec)

The latest search processing time (in seconds) of the searcher

Item Displayed	Explanation
(1) Type	Process type One of the following is displayed for the process type: Searcher AlternativeSearcher
(2) ID	Searcher identifier
(3) Hostname	Host name or IP address of the searcher
(4) State	Operating status of the searcher The operating status of the searcher is displayed as follows: ACTIVE: Running ACTIVATING: Starting up INACTIVE: Stopped
(5) Records	Number of records that can be searched
(6) DataSize	Amount of data that can be searched
(7) LatestTime(sec)	The latest search processing time (in seconds) of the searcher

Example 7

In the following example, information for the searchers connected to the director is output in CSV format.
shundstate -s shund1 -p -C > C:\shunwork\monitor\dirstate.csv

shundstate -s shund1 -p -C > /home/shunsaku/monitor/dirstate.csv

Content of dirstate.csv

"Type","ID","Hostname","State","Records","DataSize","LatestTime(sec)"
"Searcher","shuns04"," SchSvr04","INACTIVE",0,0,0.000
"Searcher","shuns03"," SchSvr03","ACTIVE",50000,12582912,0.910
"Searcher","shuns02"," SchSvr02","ACTIVE",50000,12582912,0.890
"Searcher","shuns01"," SchSvr01","ACTIVE",50000,12582912,0.900
"AlternativeSearcher","shuns05","SchWSvr01","ACTIVE",50000,12582912,0.900

Column headings are output in the first line, and information for the searchers connected to the director is output from the second line.
The values in the "DataSize" column are displayed in bytes.
Each record ends with a linefeed code.

CSV files are output using the following format:

Enclose character string items in double quotes (").
Do not enclose numerical values in double quotes (").

Information about searchers connected to the director may not be accurate when the operational status of the director is one of the following:

ACTIVATING
DEGRADING
SWITCHING
WAITING

Contents Index