-
Notifications
You must be signed in to change notification settings - Fork 76
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
Zl/handle and expose solr request timeout config and prevent crashes #572
Zl/handle and expose solr request timeout config and prevent crashes #572
Conversation
…py_data request_handler test * make ping HEAD request and make sure build true is not sent async if we cannot ping solr on iteration
c10b818
to
97960b6
Compare
eb9423c
to
0808117
Compare
|
||
-spec write_objs([node()], bucket()) -> ok. | ||
write_objs(Cluster, Bucket) -> | ||
lager:info("Writing 1000 objects"), |
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.
I'd prefer to have the number of objects be a parameter to the function instead of hard coded. Maybe there could be a write_objs/3
that takes the parameter and write_objs/2
could call that function with 1000
as an argument?
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.
Sure.. I was just keeping w/ what we had, but sure.
9b48994
to
96ca5f2
Compare
👍 96ca5f2 |
@borshop merge |
…timeout-config-and-prevent-crashes Zl/handle and expose solr request timeout config and prevent crashes Reviewed-by: jvoegele
@borshop merge |
@JeetKunDoug @fadushin
Related to Riak-2068.
entropy_data
Solr request to preventtimedout
crash during iteration or allowing the build to pass if an error occurs in iterating over the tree or if solr was not pingable.solr_request_timeout
configurable, which is used by all Solr localhost http request and add macro timeout toentropy_data
call.After some testing around, I'd like to bring-in some of these "new work" changes for 2.1.2, and a new test, since we'll be testing the release again. I think they are minor, but go along w/ the cover + java/ed/base64 changes we've already added.
Tell me if I'm wrong, but I think this is a win-win and worth it. No others, otherwise :).
Even though, we're working through #565, I will backport/cherry-pick (-x) these for 2.0 after review for clarity.