Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The state of each server node is inconsistent #8760

Open
wangyushuai opened this issue Sep 28, 2020 · 3 comments
Open

The state of each server node is inconsistent #8760

wangyushuai opened this issue Sep 28, 2020 · 3 comments
Labels
type/question Not an "enhancement" or "bug". Please post on discuss.hashicorp

Comments

@wangyushuai
Copy link

wangyushuai commented Sep 28, 2020

Overview of the Issue

Node Az2-1 thinks that the state of node AZ2-0 is leaving, but the state of node AZ2-0 in the master node or other nodes except Az2-1 is alive. What is the reason for this? What should be done?

  • Az2-0 query:

image

  • But Az2-1 query:
    image

Log Fragments

  1. AZ2-0:
    2020/09/15 11:26:05 [ERR] yamux: Failed to write header: write tcp 10.0.0.9:8300->10.0.0.7:58123: use of closed network connection
    2020/09/22 01:09:54 [ERR] raft-net: Failed to flush response: write tcp 10.0.0.9:8300->10.0.0.11:60527: write: broken pipe
  1. AZ2-1:
2020/09/10 19:22:16 [ERR] yamux: Failed to write header: write tcp 10.0.0.8:8300->10.0.0.13:41374: use of closed network connection
2020/09/22 01:09:55 [ERR] raft-net: Failed to flush response: write tcp 10.0.0.8:8300->10.0.0.11:38522: write: broken pipe
2020/09/27 10:48:14 [ERR] consul.rpc: multiplex conn accept failed: read tcp 10.0.0.8:8300->10.0.0.6:47987: read: connection reset by peer from=10.0.0.6:47987

  1. AZ1-1 master node
    2020/09/22 01:09:54 [ERR] raft: Failed to AppendEntries to {Voter 67317135-7676-3372-7474-676f616f3231 10.0.0.8:8300}: read tcp 10.0.0.11:55225->10.0.0.8:8300: i/o timeout
@wangyushuai
Copy link
Author

@mkeeler @johncowen @rboyer

@jsosulska jsosulska added the type/question Not an "enhancement" or "bug". Please post on discuss.hashicorp label Oct 2, 2020
@jsosulska
Copy link
Contributor

Hi @wangyushuai

Thanks for posting. I don't have enough information to respond right now, so I would like to ask some questions.

  • Can you please explain your architecture? I see there are a few nodes named similarly. Are there multiple NIC cards?
  • Is there a reason you are running 1.4.4? This is a very old version
  • Have you tried to restart the agent on that node?

@wangyushuai
Copy link
Author

wangyushuai commented Oct 12, 2020

Hi @wangyushuai

Thanks for posting. I don't have enough information to respond right now, so I would like to ask some questions.

  • Can you please explain your architecture? I see there are a few nodes named similarly. Are there multiple NIC cards?
  • Is there a reason you are running 1.4.4? This is a very old version
  • Have you tried to restart the agent on that node?

Hi @jsosulska , thanks for your reply

  1. Each node in the screenshot is a server node. Each server node is in a different docker container. Az1-0 and Az2-0 nodes represent different zones server nodes;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/question Not an "enhancement" or "bug". Please post on discuss.hashicorp
Projects
None yet
Development

No branches or pull requests

2 participants