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

"Multimaster node is not online: current status InMinor" #31

Open
meagon opened this issue Sep 17, 2016 · 4 comments
Open

"Multimaster node is not online: current status InMinor" #31

meagon opened this issue Sep 17, 2016 · 4 comments

Comments

@meagon
Copy link

meagon commented Sep 17, 2016

I've got this problem while use psql query, i do not known what was the problem

ERROR:  Multimaster node is not online: current status InMinor
@knizhnik
Copy link
Contributor

It means that multimaster node is not able to establish connection with other nodes.
Please check log file.

@meagon
Copy link
Author

meagon commented Sep 17, 2016

both node are starts welll, will if node lost connection as some time, it will auto reconnect?

@knizhnik
Copy link
Contributor

Yes. Actually it is better to have at least 3 nodes, because in case of failure of any of two nodes there will be no quorum and remaining node can not proceed requests.

@meagon
Copy link
Author

meagon commented Sep 17, 2016

I did it with 2 nodes, and my wal sender process becomes in

wal sender process postgres 192.168.56.103(37494) idle in transaction

when i use ps -ef |grep postgres show the command line process name ?
is it an problem?
and 2 nodes keep alive

u mean the raft port should connect ok ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants