-
Notifications
You must be signed in to change notification settings - Fork 1k
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
feat: ignore managed_service_info flag for cluster #4803
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
06ff9fa
to
60f86d1
Compare
@adiholden maybe we need to change our behavior a little for privilege connection and show all replicas independently on their health status? |
@@ -68,7 +68,7 @@ ClusterShardInfos GetConfigForStats(ConnectionContext* cntx) { | |||
CHECK(ClusterConfig::Current() != nullptr); | |||
|
|||
auto config = ClusterConfig::Current()->GetConfig(); | |||
if (cntx->conn()->IsPrivileged() || !absl::GetFlag(FLAGS_managed_service_info)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So when community users run dragonfly, this flag is false by default.
In this case cluster node we will not expose the replicas? why?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it will expose replicas only for admin connections
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As I understand we want to ignore this flag
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but why do you want to expose replicas only for admin connections for community?
This is not the expected behaviour for community running dragonfly cluster
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will fix
f398cf8
to
266ef41
Compare
managed_service_info is ignored for the cluster because we have "hidden" health status for the replica