Can't activate VR nodes after add them successfully

28 views
Skip to first unread message

liyi...@163.com

unread,
Jan 31, 2019, 10:36:56 AM1/31/19
to QFS Development
Hi Michael,

I'm trying to set up a VR system with the latest codes.
I have already setup one meta server and other 9 chunk servers. All are working well.

Now I added other two meta servers. I followed your configuration steps till the last step:

qfsadmin -f qfsadmin.cfg -s qfsmeta.mydomain.com -p 20000 -F op-type=activate-nodes -F arg-count=3 -F args='0 1 2' -v vr_reconfiguration

The log is:

01-31-2019 06:55:33.358 DEBUG - version: master--RelWithDebInfo-E1EC0D8D master-/@
01-31-2019 06:55:33.363 DEBUG - (KfsNetClient.cc:1771) add resolved: qfsmeta.mydomain.com 20000 => 10.200.132.46 20000 active: 0 total: 0 resolver: 0
01-31-2019 06:55:33.363 DEBUG - (KfsNetClient.cc:1771) add resolved: qfsmeta.mydomain.com 20000 => 10.200.132.47 20000 active: 0 total: 0 resolver: 0
01-31-2019 06:55:33.363 DEBUG - (KfsNetClient.cc:1771) add resolved: qfsmeta.mydomain.com 20000 => 10.200.132.48 20000 active: 0 total: 0 resolver: 0
01-31-2019 06:55:33.363 DEBUG - (NetConnection.cc:100) netconn: -1 resolved: 10.200.132.46 20000 status: 0
01-31-2019 06:55:33.363 DEBUG - (NetConnection.cc:100) netconn: -1 resolved: 10.200.132.47 20000 status: 0
01-31-2019 06:55:33.363 DEBUG - (NetConnection.cc:100) netconn: -1 resolved: 10.200.132.48 20000 status: 0
01-31-2019 06:55:33.363 DEBUG - (KfsNetClient.cc:1258) VR checker: 10.200.132.46 20000 connected, sending request
01-31-2019 06:55:33.363 DEBUG - (KfsNetClient.cc:1258) VR checker: 10.200.132.47 20000 connected, sending request
01-31-2019 06:55:33.363 DEBUG - (KfsNetClient.cc:1258) VR checker: 10.200.132.48 20000 connected, sending request
01-31-2019 06:55:33.363 DEBUG - (KfsNetClient.cc:1706) VR primary: 10.200.132.46 20000
01-31-2019 06:55:33.363 DEBUG - (KfsNetClient.cc:2334) connecting to server: 10.200.132.46 20000 auth: off
01-31-2019 06:55:33.363 DEBUG - (MonClient.cc:184) op completed: VR_RECONFIGURATION status: -22 status: -22 Invalid argument 22 msg: change active status: channels down: 1 2
01-31-2019 06:55:33.363 ERROR - (qfsadmin_main.cc:277) change active status: channels down: 1 2 error: Invalid argument 22

Adding nodes return status 0, means successful.
file system and logs were also synchronized from primary node.
chunk servers were not started (I tried start them but didn't help).

I have a DNS server that has three entries to return three IPs for "qfsmeta.mydomain.com". nslookup result can see all IPs are returned for the same name.

I have no idea what is the possible error?

Plus vr_get_status result:

vr.nodeId: 0
vr.status: 0
vr.active: 0
vr.state: primary
vr.primaryId: 0
vr.epoch: 0
vr.view: 0
vr.log: 0 0 3
vr.commit: 0 0 3
vr.lastViewEnd: -1 -1 -1
vr.quorum: 0
vr.ignoreInvalidVrState: 0
vr.fileSystemId: 6844114206966418128
vr.clusterKey: test-qfs-identifier
vr.metaMd5: 169be096330c6cd8fa57413715b0e4c1
vr.viewChangeReason: restart
vr.viewChangeStartTime: 0
vr.currentTime: 1548947521

logTransmitter.channel.0.location: 10.200.132.48 32000
logTransmitter.channel.0.id: 2
logTransmitter.channel.0.receivedId: 2
logTransmitter.channel.0.primaryId: 0
logTransmitter.channel.0.active: 0
logTransmitter.channel.0.ack: 0 0 0
logTransmitter.channel.0.sent: 0 0 3
logTransmitter.channel.0.ctrs.op5SecAvgUsec: 0
logTransmitter.channel.0.ctrs.op10SecAvgUsec: 0
logTransmitter.channel.0.ctrs.op15SecAvgUsec: 0
logTransmitter.channel.0.ctrs.opAvgUsec: 0
logTransmitter.channel.0.ctrs.op5SecAvgRate: 0
logTransmitter.channel.0.ctrs.op10SecAvgRate: 0
logTransmitter.channel.0.ctrs.op15SecAvgRate: 0
logTransmitter.channel.0.ctrs.opsTotal: 0
logTransmitter.channel.0.ctrs.opsTimeTotalUsec: 0
logTransmitter.channel.0.ctrs.5SecAvgPendingOps: 0
logTransmitter.channel.0.ctrs.10SecAvgPendingOps: 0
logTransmitter.channel.0.ctrs.15SecAvgPendingOps: 0
logTransmitter.channel.0.ctrs.pendingOps: 0
logTransmitter.channel.0.ctrs.5SecAvgPendingBytes: 0
logTransmitter.channel.0.ctrs.10SecAvgPendingBytes: 0
logTransmitter.channel.0.ctrs.15SecAvgPendingBytes: 0
logTransmitter.channel.0.ctrs.pendingBytes: 0
logTransmitter.channel.1.location: 10.200.132.47 32000
logTransmitter.channel.1.id: 1
logTransmitter.channel.1.receivedId: 1
logTransmitter.channel.1.primaryId: 0
logTransmitter.channel.1.active: 0
logTransmitter.channel.1.ack: 0 0 0
logTransmitter.channel.1.sent: 0 0 3
logTransmitter.channel.1.ctrs.op5SecAvgUsec: 0
logTransmitter.channel.1.ctrs.op10SecAvgUsec: 0
logTransmitter.channel.1.ctrs.op15SecAvgUsec: 0
logTransmitter.channel.1.ctrs.opAvgUsec: 0
logTransmitter.channel.1.ctrs.op5SecAvgRate: 0
logTransmitter.channel.1.ctrs.op10SecAvgRate: 0
logTransmitter.channel.1.ctrs.op15SecAvgRate: 0
logTransmitter.channel.1.ctrs.opsTotal: 0
logTransmitter.channel.1.ctrs.opsTimeTotalUsec: 0
logTransmitter.channel.1.ctrs.5SecAvgPendingOps: 0
logTransmitter.channel.1.ctrs.10SecAvgPendingOps: 0
logTransmitter.channel.1.ctrs.15SecAvgPendingOps: 0
logTransmitter.channel.1.ctrs.pendingOps: 0
logTransmitter.channel.1.ctrs.5SecAvgPendingBytes: 0
logTransmitter.channel.1.ctrs.10SecAvgPendingBytes: 0
logTransmitter.channel.1.ctrs.15SecAvgPendingBytes: 0
logTransmitter.channel.1.ctrs.pendingBytes: 0
logTransmitter.channel.2.location: 10.200.132.46 32000
logTransmitter.channel.2.id: 0
logTransmitter.channel.2.receivedId: 0
logTransmitter.channel.2.primaryId: 0
logTransmitter.channel.2.active: 0
logTransmitter.channel.2.ack: 0 0 3
logTransmitter.channel.2.sent: 0 0 3
logTransmitter.channel.2.ctrs.op5SecAvgUsec: 0
logTransmitter.channel.2.ctrs.op10SecAvgUsec: 0
logTransmitter.channel.2.ctrs.op15SecAvgUsec: 0
logTransmitter.channel.2.ctrs.opAvgUsec: 0
logTransmitter.channel.2.ctrs.op5SecAvgRate: 0
logTransmitter.channel.2.ctrs.op10SecAvgRate: 0
logTransmitter.channel.2.ctrs.op15SecAvgRate: 0
logTransmitter.channel.2.ctrs.opsTotal: 0
logTransmitter.channel.2.ctrs.opsTimeTotalUsec: 0
logTransmitter.channel.2.ctrs.5SecAvgPendingOps: 0
logTransmitter.channel.2.ctrs.10SecAvgPendingOps: 0
logTransmitter.channel.2.ctrs.15SecAvgPendingOps: 0
logTransmitter.channel.2.ctrs.pendingOps: 0
logTransmitter.channel.2.ctrs.5SecAvgPendingBytes: 0
logTransmitter.channel.2.ctrs.10SecAvgPendingBytes: 0
logTransmitter.channel.2.ctrs.15SecAvgPendingBytes: 0
logTransmitter.channel.2.ctrs.pendingBytes: 0

logTransmitter.activeUpNodesCount: 0
logTransmitter.activeUpChannelsCount: 0

configuration.primaryTimeout: 4
configuration.backupTimeout: 8
configuration.changeViewMaxLogDistance: 131072
configuration.maxListenersPerNode: 16
configuration.node.0.id: 0
configuration.node.0.flags: 0
configuration.node.0.active: 0
configuration.node.0.primaryOrder: 0
configuration.node.0.listener: 10.200.132.46 32000
configuration.node.1.id: 1
configuration.node.1.flags: 0
configuration.node.1.active: 0
configuration.node.1.primaryOrder: 0
configuration.node.1.listener: 10.200.132.47 32000
configuration.node.2.id: 2
configuration.node.2.flags: 0
configuration.node.2.active: 0
configuration.node.2.primaryOrder: 0
configuration.node.2.listener: 10.200.132.48 32000


Thanks!

Michael Ovsiannikov

unread,
Feb 8, 2019, 11:03:51 PM2/8/19
to <qfs-devel@googlegroups.com>
Hello,

I think that the following might help:

https://github.com/quantcast/qfs/issues/223

— Mike.

--
You received this message because you are subscribed to the Google Groups "QFS Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qfs-devel+...@googlegroups.com.
To post to this group, send email to qfs-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qfs-devel/a6c40b35-0a9a-443e-9dfa-72fcaed4adc0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages