You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 28, 2022. It is now read-only.
Hi,
First of all, I'd like to thank you for making pilosa OS and available freely.
We have been using 2.0 from master branch for a while now.
During write operations if the cluster is not in ready state is it possible to handle these without throwing exceptions? A check prior to every operation might be costly, but how about providing a subscription end point on the server side to broadcast a state like writablereadableunavailable
The text was updated successfully, but these errors were encountered:
I wanted to acknowledge this issue, but warn you that it might be a while before someone is able to tackle this. The core team is laser focused on tasks which directly contribute to generating revenue for the business during these uncertain times (global pandemic, etc. etc.)
Thank you for your understanding! Hopefully we'll have more bandwidth soon :)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
First of all, I'd like to thank you for making pilosa OS and available freely.
We have been using 2.0 from master branch for a while now.
During write operations if the cluster is not in ready state is it possible to handle these without throwing exceptions? A check prior to every operation might be costly, but how about providing a subscription end point on the server side to broadcast a state like
writable
readable
unavailable
The text was updated successfully, but these errors were encountered: