We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
juju deploy ./*charm --config role="config-server" config-server-one -n2 juju deploy ./*charm --config role="shard" shard-one -n2 juju deploy ./*charm --config role="shard" shard-two -n2 juju integrate config-server-one:config-server shard-one:sharding juju integrate config-server-one:config-server shard-two:sharding juju remove-relation config-server-one:config-server shard-two:sharding
the last unit of shard-two to report active and running
shard-two
the last unit of shard-two reports it is still being added to the cluster
This is happening because we check if a shard has been added by relation data
Actually ask mongodb if the shard has been added instead of checking a boolean flag
The text was updated successfully, but these errors were encountered:
https://warthogs.atlassian.net/browse/DPE-2890
Sorry, something went wrong.
fix bugs (#299)
1d35616
## Issue We have several bugs in the sharding implementation, fix them #297 #301 #302
No branches or pull requests
Steps to reproduce
Expected behavior
the last unit of
shard-two
to report active and runningActual behavior
the last unit of
shard-two
reports it is still being added to the clusterwhy this is happening
This is happening because we check if a shard has been added by relation data
proposed fix
Actually ask mongodb if the shard has been added instead of checking a boolean flag
The text was updated successfully, but these errors were encountered: