-
Notifications
You must be signed in to change notification settings - Fork 440
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
what mean about PG WANTEDGENERATION and PG CURRENTGENERATION #881
Comments
I agree, that it would be nice to improve the documentation around these internal concepts. Let me explain what I understand. When the db spec changes, sentinel increases the db.Generation by 1. stolon/cmd/sentinel/cmd/sentinel.go Line 1560 in e48f9a4
If the keeper is healthy, then it would likely update the spec change and finally keeper sets local status with db.generation. stolon/cmd/keeper/cmd/keeper.go Line 1741 in 5dc6358
Keeper reports the updated local state generation and sentinel updates db.status.currentGeneration with db.generation stolon/cmd/sentinel/cmd/sentinel.go Line 301 in e48f9a4
Overall, why we doing all these is a way to identify that whether the databases (keepers) are converged or not. @sgotti feel free to correct me wherever I am wrong :) |
@viggy28 Thanks,I got it |
I just learned the stolon framework, and I encountered some concepts that I don't understand very well, and I didn't find any relevant explanations in the relevant documents.
When I use the
stolonctl status
command to get the cluster status, I see the following two columns in the status of the keepers. I don't know what it means. The two values are sometimes the same, sometimes different. What does the same value mean? What's the difference?PG WANTEDGENERATION PG CURRENTGENERATION
The text was updated successfully, but these errors were encountered: