Aクラスター上で実行するB機能では，B機能を実行したノードで登録処理は行われず，必ずMasterノードで行われるということでしょうか？
私がログを見る限りにおいては，B機能実行時にSlave状態であるNode2から，同じくSlave状態であるNode9に対して接続できないエラーが発生しています。
そのため，私の解釈では，Node2がB機能を実行し，そのデータをNode9に渡そうとした時にエラーになっているのではないかと思っていました。
Rating
50
Translation / English
- Posted at 14 Aug 2020 at 10:27
B function executes on A cluster is not registered by Node carried B function, and do you mean it is done by Master Node without doubt?
As far as I can see the log, when B function is carried out, from Node2 in a state of Slave, against the same Slave state Node9, there is an error that cannot be connected.
Therefore, to my understanding, when Node2 is carried out B function and pass the data to Node 9, it makes an error.
issei2029 likes this translation
As far as I can see the log, when B function is carried out, from Node2 in a state of Slave, against the same Slave state Node9, there is an error that cannot be connected.
Therefore, to my understanding, when Node2 is carried out B function and pass the data to Node 9, it makes an error.
![[deleted user]](https://secure.gravatar.com/avatar/695023b4efd563721d13716b1457bc73.png?d=identicon&mode=crop&r=PG&s=42)
Rating
52
Translation / English
- Posted at 14 Aug 2020 at 10:30
Can I make sure that the registration process isn't conducted on the node where the B function executed but conducted on the master node, right?
As far as I have seen a log, there are errors: the failed establishment of connection occurred from Node2 on the state of Slave on running B function to Node9 where on the state of Slave.
Therefore, for my understanding, I thought there would be errors when the B function was implemented at the Node2 and trying to transfer the data to Node9.
issei2029 likes this translation
As far as I have seen a log, there are errors: the failed establishment of connection occurred from Node2 on the state of Slave on running B function to Node9 where on the state of Slave.
Therefore, for my understanding, I thought there would be errors when the B function was implemented at the Node2 and trying to transfer the data to Node9.
もしNode9がデータを受け取れなかった場合でも，MasterであるNode1がデータを受け取れていれば，Node9はいつかNode1と同期されるので問題ないと思っていますが，MasterであるNode1がデータを受け取れない場合は，SlaveはいつかMasterと同期されるので問題だと思っています。
もう一度ログを精査して，原因を突き止めたいと思っていますが，その前にAクラスターにおけるデータ登録の解釈はこれで合っているかコメントいただけますでしょうか？
Rating
50
Translation / English
- Posted at 14 Aug 2020 at 10:33
Even if f Node9 cannot get data, Master Node1 obtains data, Node9 would be corresponded with Node1some day, I suppose, but if Master Node1 cannot get the data, Slave would be corresponded withMaster some day, I suppose.
Once again to see the log clearly, I would like to find the reason, but beforehand, could you please comment if A cluster's data registration understanding is correct or not?
issei2029 likes this translation
Once again to see the log clearly, I would like to find the reason, but beforehand, could you please comment if A cluster's data registration understanding is correct or not?
Rating
52
Translation / English
- Posted at 14 Aug 2020 at 10:35
Unless Node9 receives the data, if Node1 as master receives the data, I do believe there are no worries because Node9 is synchronised with Node1. But if Node1 as master cannot receive the data, Slave might be synchronised to the master soon and that makes me a problematic issue.
I want to try to find out the cause as I will check the data through, but could you give me your comment for my understanding of the data registration on A cluster, please?
issei2029 likes this translation
I want to try to find out the cause as I will check the data through, but could you give me your comment for my understanding of the data registration on A cluster, please?
