検証は、次のことに使用できるツールです。
ストアの一般的なトラブルシューティングを行います。
検証では、ストアのすべてのコンポーネントを検査します。すべてのストアのサービスが使用可能かどうか、それらのサービスでバージョンまたはメタデータの不一致があるかどうかもチェックされます。
長時間実行されているプランのステータスをチェックします。
プランの中には、多数のステップが必要で、実行に時間がかかるものもあります。管理者はプランを検証して、プランの進捗を確認したり、ERROR状態のプランの診断に役立てることができます。たとえば、Deploy Storeプランが多数のストレージ・ノードに対して実行されているときにこのプランを検証できます。検証レポートを参照すると、反復ごとにノードが作成されて起動されたことを確認できます。
プランの管理方法の詳細は、「プラン」を参照してください。
ERROR状態のプランに関する追加情報を提供します。
CLIのverifyコマンドを使用してストアの検証を実行します。パラメータは不要で、デフォルトでは冗長モードで実行されます。次に例を示します。
kv-> verify configuration
Verify: starting verification of store MetroArea based upon
topology sequence #117
100 partitions and 6 storage nodes
Time: 2015-06-16 00:01:05 UTC Version: 12.1.3.4.0
See node01:Data/virtualroot/datacenter1/kvroot/MetroArea/
log/MetroArea_{0..N}.log for
progress messages
Verify: Shard Status: healthy:2 writable-degraded:0
read-only:0 offline:0
Verify: Admin Status: healthy
Verify: Zone [name=Manhattan id=zn1 type=PRIMARY]
RN Status: online:2 offline: 0 maxDelayMillis:1 maxCatchupTimeSecs:0
Verify: Zone [name=JerseyCity id=zn2 type=PRIMARY]
RN Status: online:2 offline: 0 maxDelayMillis:1 maxCatchupTimeSecs:0
Verify: Zone [name=Queens id=zn3 type=PRIMARY]
RN Status: online:2 offline: 0
Verify: == checking storage node sn1 ==
Verify: Storage Node [sn1] on node01:5000
Zone: [name=Manhattan id=zn1 type=PRIMARY] Status: RUNNING
Ver: 12cR1.3.4.0 2015-05-29 12:09:04 UTC Build id: db9ec397225c
Verify: Admin [admin1] Status: RUNNING,MASTER
Verify: Rep Node [rg1-rn2] Status: RUNNING,REPLICA
sequenceNumber:127 haPort:5011 delayMillis:1 catchupTimeSecs:0
Verify: == checking storage node sn2 ==
Verify: Storage Node [sn2] on node02:6000
Zone: [name=Manhattan id=zn1 type=PRIMARY] Status: RUNNING
Ver: 12cR1.3.4.0 2015-05-29 12:09:04 UTC Build id: db9ec397225c
Verify: Rep Node [rg2-rn2] Status: RUNNING,REPLICA
sequenceNumber:127 haPort:6010 delayMillis:1 catchupTimeSecs:0
Verify: == checking storage node sn3 ==
Verify: Storage Node [sn3] on node03:7000
Zone: [name=JerseyCity id=zn2 type=PRIMARY] Status: RUNNING
Ver: 12cR1.3.4.0 2015-05-29 12:09:04 UTC Build id: db9ec397225c
Verify: Admin [admin2] Status: RUNNING,REPLICA
Verify: Rep Node [rg1-rn3] Status: RUNNING,REPLICA
sequenceNumber:127 haPort:7011 delayMillis:1 catchupTimeSecs:0
Verify: == checking storage node sn4 ==
Verify: Storage Node [sn4] on node04:8000
Zone: [name=JerseyCity id=zn2 type=PRIMARY] Status: RUNNING
Ver: 12cR1.3.4.0 2015-05-29 12:09:04 UTC Build id: db9ec397225c
Verify: Rep Node [rg2-rn3] Status: RUNNING,REPLICA
sequenceNumber:127 haPort:8010 delayMillis:1 catchupTimeSecs:0
Verify: == checking storage node sn5 ==
Verify: Storage Node [sn5] on node05:9000
Zone: [name=Queens id=zn3 type=PRIMARY] Status: RUNNING
Ver: 12cR1.3.4.0 2015-05-29 12:09:04 UTC Build id: db9ec397225c
Verify: Admin [admin3] Status: RUNNING,REPLICA
Verify: Rep Node [rg1-rn1] Status: RUNNING,MASTER
sequenceNumber:127 haPort:9011
Verify: == checking storage node sn6 ==
Verify: Storage Node [sn6] on node06:10000
Zone: [name=Queens id=zn3 type=PRIMARY] Status: RUNNING
Ver: 12cR1.3.4.0 2015-05-29 12:09:04 UTC Build id: db9ec397225c
Verify: Rep Node [rg2-rn1] Status: RUNNING,MASTER
sequenceNumber:127 haPort:10010
Verification complete, no violations.
問題のみを表示するサイレント・モードを使用できます。
kv-> verify configuration -silent
Verify: starting verification of store MetroArea based upon
topology sequence #117
100 partitions and 6 storage nodes
Time: 2015-06-16 04:00:02 UTC Version: 12.1.3.4.0
See node01:Data/virtualroot/datacenter1/kvroot/MetroArea/
log/MetroArea_{0..N}.log for progress messages
Verification complete, no violations.
ストアの問題が明確にレポートされます。たとえば、ストレージ・ノードが使用不能な場合、サイレント・モードでは、問題が次のように表示されます。
kv-> verify configuration -silent
Verify: starting verification of store MetroArea based upon
topology sequence #117
100 partitions and 6 storage nodes
Time: 2015-06-16 04:09:18 UTC Version: 12.1.3.4.0
See node01:Data/virtualroot/datacenter1/kvroot/MetroArea/
log/MetroArea_{0..N}.log for progress messages
Verification complete, 2 violations, 0 notes found.
Verification violation: [rg2-rn2] ping() failed for rg2-rn2 :
Unable to connect to the storage node agent at host node02, port 6000,
which may not be running; nested exception is:
java.rmi.ConnectException: Connection refused to host: node02;
nested exception is:
java.net.ConnectException: Connection refused
Verification violation: [sn2] ping() failed for sn2 : Unable to connect
to the storage node agent at host node02, port 6000,
which may not be running; nested exception is:
java.rmi.ConnectException: Connection refused to host: node02;
nested exception is:
java.net.ConnectException: Connection refused
冗長モードでは、前述の問題が次のように表示されます。
kv-> verify configuration
Verify: starting verification of store MetroArea based upon
topology sequence #117
100 partitions and 6 storage nodes
Time: 2015-06-16 04:17:31 UTC Version: 12.1.3.4.0
See node01:Data/virtualroot/datacenter1/kvroot/MetroArea/
log/MetroArea_{0..N}.log for progress messages
Verify: Shard Status: healthy:1 writable-degraded:1
read-only:0 offline:0
Verify: Admin Status: healthy
Verify: Zone [name=Manhattan id=zn1 type=PRIMARY]
RN Status: online:1 offline: 1 maxDelayMillis:1 maxCatchupTimeSecs:0
Verify: Zone [name=JerseyCity id=zn2 type=PRIMARY]
RN Status: online:2 offline: 0 maxDelayMillis:1 maxCatchupTimeSecs:0
Verify: Zone [name=Queens id=zn3 type=PRIMARY]
RN Status: online:2 offline: 0
Verify: == checking storage node sn1 ==
Verify: Storage Node [sn1] on node01:5000
Zone: [name=Manhattan id=zn1 type=PRIMARY] Status: RUNNING
Ver: 12cR1.3.4.0 2015-05-29 12:09:04 UTC Build id: db9ec397225c
Verify: Admin [admin1] Status: RUNNING,MASTER
Verify: Rep Node [rg1-rn2] Status: RUNNING,REPLICA
sequenceNumber:127 haPort:5011 delayMillis:1 catchupTimeSecs:0
Verify: == checking storage node sn2 ==
Verify: sn2: ping() failed for sn2 :
Unable to connect to the storage node agent at host node02, port 6000,
which may not be running; nested exception is:
java.rmi.ConnectException: Connection refused to host: node02;
nested exception is:
java.net.ConnectException: Connection refused
Verify: Storage Node [sn2] on node02:6000
Zone: [name=Manhattan id=zn1 type=PRIMARY] UNREACHABLE
Verify: rg2-rn2: ping() failed for rg2-rn2 :
Unable to connect to the storage node agent at host node02, port 6000,
which may not be running; nested exception is:
java.rmi.ConnectException: Connection refused to host: node02;
nested exception is:
java.net.ConnectException: Connection refused
Verify: Rep Node [rg2-rn2] Status: UNREACHABLE
Verify: == checking storage node sn3 ==
Verify: Storage Node [sn3] on node03:7000
Zone: [name=JerseyCity id=zn2 type=PRIMARY] Status: RUNNING
Ver: 12cR1.3.4.0 2015-05-29 12:09:04 UTC Build id: db9ec397225c
Verify: Admin [admin2] Status: RUNNING,REPLICA
Verify: Rep Node [rg1-rn3] Status: RUNNING,REPLICA
sequenceNumber:127 haPort:7011 delayMillis:1 catchupTimeSecs:0
Verify: == checking storage node sn4 ==
Verify: Storage Node [sn4] on node04:8000
Zone: [name=JerseyCity id=zn2 type=PRIMARY] Status: RUNNING
Ver: 12cR1.3.4.0 2015-05-29 12:09:04 UTC Build id: db9ec397225c
Verify: Rep Node [rg2-rn3] Status: RUNNING,REPLICA
sequenceNumber:127 haPort:8010 delayMillis:0 catchupTimeSecs:0
Verify: == checking storage node sn5 ==
Verify: Storage Node [sn5] on node05:9000
Zone: [name=Queens id=zn3 type=PRIMARY] Status: RUNNING
Ver: 12cR1.3.4.0 2015-05-29 12:09:04 UTC Build id: db9ec397225c
Verify: Admin [admin3] Status: RUNNING,REPLICA
Verify: Rep Node [rg1-rn1] Status: RUNNING,MASTER
sequenceNumber:127 haPort:9011
Verify: == checking storage node sn6 ==
Verify: Storage Node [sn6] on node06:10000
Zone: [name=Queens id=zn3 type=PRIMARY] Status: RUNNING
Ver: 12cR1.3.4.0 2015-05-29 12:09:04 UTC Build id: db9ec397225c
Verify: Rep Node [rg2-rn1] Status: RUNNING,MASTER
sequenceNumber:127 haPort:10010
Verification complete, 2 violations, 0 notes found.
Verification violation: [rg2-rn2] ping() failed for rg2-rn2 :
Unable to connect to the storage node agent at host node02, port 6000,
which may not be running; nested exception is:
java.rmi.ConnectException: Connection refused to host: node02;
nested exception is:
java.net.ConnectException: Connection refused
Verification violation: [sn2] ping() failed for sn2 :
Unable to connectto the storage node agent at host node02, port 6000,
which may not be running; nested exception is:
java.rmi.ConnectException: Connection refused to host: node02;
nested exception is:
java.net.ConnectException: Connection refused
検証の出力は、コマンドの終了時にのみシェルに表示されます。検証の進捗を確認するには、Oracle NoSQL Databaseのログ・ファイルに対してtailまたはgrepを使用します。文字列Verifyを検索します。次に例を示します。
grep Verify /KVRT1/mystore/log/mystore_0.log