Linux でAクラスターを10台構成で組んでいます。（便宜上これを Node1 から Node10 と呼ぶことにします）
データの登録は常にNode2のB機能を使っています。従って、B機能の実行はNode2がMasterの時もあれば、Slaveの時もあります。B機能実行時にNode2を強制的にMasterにする操作はしていません。
ある時、Node2がSlaveの状態でB機能を実行したら、Node9に対する以下のエラーが発生しました。
- エラー -
評価
52
翻訳 / 英語
- 2020/08/13 22:51:36に投稿されました
It consists of 10 units of A cluster by Linux(For making you understand well, this will be called Node1 to Node10 here for you.)
The storing the data uses the B function at Node2 always. Therefore, the execution of B function either Master or Slave for node2. When running with B function, we never operate make Node2 as a master.
But running B function on the state of Slave on Node2 occurs the following error towards Node9 someday.
-Error
The storing the data uses the B function at Node2 always. Therefore, the execution of B function either Master or Slave for node2. When running with B function, we never operate make Node2 as a master.
But running B function on the state of Slave on Node2 occurs the following error towards Node9 someday.
-Error
評価
50
翻訳 / 英語
- 2020/08/13 22:51:17に投稿されました
We have 10 A clusters in Linux. (We will call this Node1 to Node10 for convenience)
Data registration always uses B function of Node2. Therefore, the B function may be executed when Node2 is Master or Slave. Node 2 is not forcibly set to Master when the B function is executed.
At one point, when Node2 executed the B function in the Slave state, the following error in Node9 occurred.
-Error-
Data registration always uses B function of Node2. Therefore, the B function may be executed when Node2 is Master or Slave. Node 2 is not forcibly set to Master when the B function is executed.
At one point, when Node2 executed the B function in the Slave state, the following error in Node9 occurred.
-Error-
このエラーは極たまに発生し、再現性がなく、調査が難航しています。
何か考えられる原因はないでしょうか？Linuxのアンチパターンを踏んでいないか気になっています。
心配しているのはNode2がB機能を実行した時、MasterであるNode1に対して上記のエラーが発生すると、
暫くしたら全てのノードがNode1の状態に戻ってしまうのではないかということです。
この認識で正しいでしょうか？
もしAクラスターでB機能を使用すること自体が良くないことなら，そのことも教えてもらえると嬉しいです。
評価
50
翻訳 / 英語
- 2020/08/13 22:45:16に投稿されました
This error occurs once a while and we have difficulty to see the problems without recovering.
Is there any reason you can think of? We are worrying about if it is doing Linux anti-pattern.
What we are worrying is, when Node 2 executes B function, to Node1 which is the master, it shows the above error, and in a meantime, all nodes return to Node1.
Is this a correct to understand?
If it is not good for us to use B function by A cluster, please tell us about it too.
Is there any reason you can think of? We are worrying about if it is doing Linux anti-pattern.
What we are worrying is, when Node 2 executes B function, to Node1 which is the master, it shows the above error, and in a meantime, all nodes return to Node1.
Is this a correct to understand?
If it is not good for us to use B function by A cluster, please tell us about it too.
評価
52
翻訳 / 英語
- 2020/08/13 22:45:34に投稿されました
The error occurs sometimes however it is not reproducible so that the investigation is troublesome. Is there any possible cause for this problem? I mind that it was because of the anti-pattern occurrences for Linux I suppose.
The thing is, when running B function by Node2, the above error occurs towards Node1 as a master, then soon after, all the nodes might be returning to the state of the Node1. Do you think my understanding makes sense?
If using B function at A cluster is not recommended, I am happy to teach whether.
The thing is, when running B function by Node2, the above error occurs towards Node1 as a master, then soon after, all the nodes might be returning to the state of the Node1. Do you think my understanding makes sense?
If using B function at A cluster is not recommended, I am happy to teach whether.
