What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
bug fix
What is the current behavior? (You can also link to an open issue here)
the index operations will be blocked if marqo fails to connect to Zookeeper
What is the new behavior (if this is a feature change)?
If the ZOOKEEPER_HOSTS environment variable is not set, we still allow users to conduct index operations without concurrency protection.
If the ZOOKEEPER_HOSTS environment variable is set, Marqo will block the index operations if it fails to connect the target zookeeper server.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
no
Have unit tests been run against this PR? (Has there also been any additional testing?)
no
Related Python client changes (link commit/PR here)
no
Related documentation changes (link commit/PR here)
no
Other information:
no
Please check if the PR fulfills these requirements
[ ] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes/features)
[ ] Docs have been added / updated (for bug fixes / features)
… the environment variable is no set
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...) bug fix
What is the current behavior? (You can also link to an open issue here) the index operations will be blocked if marqo fails to connect to Zookeeper
What is the new behavior (if this is a feature change)? If the
ZOOKEEPER_HOSTSenvironment variable is not set, we still allow users to conduct index operations without concurrency protection.If the
ZOOKEEPER_HOSTSenvironment variable is set, Marqo will block the index operations if it fails to connect the target zookeeper server.Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?) no
Have unit tests been run against this PR? (Has there also been any additional testing?) no
Related Python client changes (link commit/PR here) no
Related documentation changes (link commit/PR here)
no
Other information: no
Please check if the PR fulfills these requirements
[ ] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes/features)
[ ] Docs have been added / updated (for bug fixes / features)