Dear Expert,
We have migrate Memory Based-NameSpace to Quarkdb Based NameSpace for Kolkata:EOS2.
The version of eos and quarkdb are :-
EOS_SERVER_VERSION=4.8.40 EOS_SERVER_RELEASE=1
EOS_CLIENT_VERSION=4.8.40 EOS_CLIENT_RELEASE=1
QUARKDB-VERSION 0.4.2
Today we had started the QuarkDB with three hosts (i.e. eos-mgm, eos-slave and eos-qdb). It’s working fine. We also convert files.md and directories.md to QuarkDB. Then start eos@master and eos@slave with eos@mq and eos@mgm daemon in two hosts. (eos-mgm has Master role and eos-slave has SLAVE role).
It’s start fine and shown the all seven FST’s i.e.
[root@eos-mgm ~]# redis-cli -p 7777 raft-info
- TERM 192
- LOG-START 1111
- LOG-SIZE 12572
- LEADER eos-mgm.tier2-kol.res.in:7777
- CLUSTER-ID 8370db63-fdf7-4df9-807a-36a7c5692232
- COMMIT-INDEX 12571
- LAST-APPLIED 12571
- BLOCKED-WRITES 0
- LAST-STATE-CHANGE 8036 (2 hours, 13 minutes, 56 seconds)
-
- MYSELF eos-mgm.tier2-kol.res.in:7777
- VERSION 0.4.2
- STATUS LEADER
- NODE-HEALTH GREEN
- JOURNAL-FSYNC-POLICY sync-important-updates
-
- MEMBERSHIP-EPOCH 1111
- NODES eos-mgm.tier2-kol.res.in:7777,eos-slave.tier2-kol.res.in:7777,eos-qdb.tier2-kol.res.in:7777
- OBSERVERS
- QUORUM-SIZE 2
-
- REPLICA eos-qdb.tier2-kol.res.in:7777 | ONLINE | UP-TO-DATE | NEXT-INDEX 12572 | VERSION 0.4.2
- REPLICA eos-slave.tier2-kol.res.in:7777 | ONLINE | UP-TO-DATE | NEXT-INDEX 12572 | VERSION 0.4.2
[root@eos-mgm ~]#
[root@eos-mgm ~]# eos -b node ls
┌──────────┬────────────────────────────────┬────────────────┬──────────┬────────────┬──────┬──────────┬────────┬────────┬────────────────┬─────┐
│type │ hostport│ geotag│ status│ activated│ txgw│ gw-queued│ gw-ntx│ gw-rate│ heartbeatdelta│ nofs│
└──────────┴────────────────────────────────┴────────────────┴──────────┴────────────┴──────┴──────────┴────────┴────────┴────────────────┴─────┘
nodesview eos04.tier2-kol.res.in:1095 Kolkata::EOS2 online ??? off 0 10 120 0 0
nodesview eos05.tier2-kol.res.in:1095 Kolkata::EOS2 online ??? off 0 10 120 2 0
nodesview eos06.tier2-kol.res.in:1095 Kolkata::EOS2 online ??? off 0 10 120 2 0
nodesview eos07.tier2-kol.res.in:1095 Kolkata::EOS2 online ??? off 0 10 120 1 0
nodesview eos08.tier2-kol.res.in:1095 Kolkata::EOS2 online ??? off 0 10 120 0 0
nodesview eos09.tier2-kol.res.in:1095 Kolkata::EOS2 online ??? off 0 10 120 2 0
nodesview eos10.tier2-kol.res.in:1095 Kolkata::EOS2 online ??? off 0 10 120 1 0
[root@eos-mgm ~]#
Here we notice that all the seven FST’s are not activated and then we had activate all seven FSTs manually by “eos node set eos04.tier2-kol.res.in on”.
Then they are activated i.e.
++++++++++++
[root@eos-mgm ~]# eos -b node ls
┌──────────┬────────────────────────────────┬────────────────┬──────────┬────────────┬──────┬──────────┬────────┬────────┬────────────────┬─────┐
│type │ hostport│ geotag│ status│ activated│ txgw│ gw-queued│ gw-ntx│ gw-rate│ heartbeatdelta│ nofs│
└──────────┴────────────────────────────────┴────────────────┴──────────┴────────────┴──────┴──────────┴────────┴────────┴────────────────┴─────┘
nodesview eos04.tier2-kol.res.in:1095 Kolkata::EOS2 online on off 0 10 120 1 0
nodesview eos05.tier2-kol.res.in:1095 Kolkata::EOS2 online on off 0 10 120 2 0
nodesview eos06.tier2-kol.res.in:1095 Kolkata::EOS2 online on off 0 10 120 2 0
nodesview eos07.tier2-kol.res.in:1095 Kolkata::EOS2 online on off 0 10 120 1 0
nodesview eos08.tier2-kol.res.in:1095 Kolkata::EOS2 online on off 0 10 120 1 0
nodesview eos09.tier2-kol.res.in:1095 Kolkata::EOS2 online on off 0 10 120 2 0
nodesview eos10.tier2-kol.res.in:1095 Kolkata::EOS2 online on off 0 10 120 2 0
[root@eos-mgm ~]#
+++++++++++++++
Now we have check the eos space , eos group and eos fs , but there are no output. It horrifying!
[root@eos-mgm ~]# eos -b group ls
[root@eos-mgm ~]# eos -b space ls
[root@eos-mgm ~]# eos -b fs ls
[root@eos-mgm ~]#
How we can get recover those group and fs?
==================
Also, in eos-slave (SLAVE), an activated column of “eos -b node ls” are shown as “???” for all FSTs.
[root@eos-slave ~]# eos node ls
┌──────────┬────────────────────────────────┬────────────────┬──────────┬────────────┬──────┬──────────┬────────┬────────┬────────────────┬─────┐
│type │ hostport│ geotag│ status│ activated│ txgw│ gw-queued│ gw-ntx│ gw-rate│ heartbeatdelta│ nofs│
└──────────┴────────────────────────────────┴────────────────┴──────────┴────────────┴──────┴──────────┴────────┴────────┴────────────────┴─────┘
nodesview eos04.tier2-kol.res.in:1095 Kolkata::EOS2 online ??? off 0 10 120 2 0
nodesview eos05.tier2-kol.res.in:1095 Kolkata::EOS2 online ??? off 0 10 120 1 0
This is showing that, changes in eos-mgm (manager) will not reflect to eos-slave (slave).
How did eos-mgm config reflect to eos-slave?
Kindly suggest.
Regards
Prasun