-
Notifications
You must be signed in to change notification settings - Fork 15
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
Improve --text search timeouts #71
Comments
Modified (Omitting the non-responsive spv11,12,13,14,15)
Second query:
Third query:
|
Perhaps the thing to be done here is spread the load around more. It looks like the SDK selects the one with the lowest latency SPVPong response. This could be misleading, as it doesn't account for elastic search latency and other things that might go into servicing hub RPCs. Also, the hub performance could change with day of week, or time of day. I don't see a provision to react to deteriorated performance, or claim_search timeout by choosing a different hub. |
Other ideas from ES documentation: Hard to say what effect this would have. But 6 fields are being searched currently: Line 907 in 34c5ab2
|
Another observation... The Line 62 in 35483fa
However, there are API-level timeout params accepted for individual calls to ES: API-level timeout for search: The |
Here's the search invocation (no timeout=X): Line 208 in 34c5ab2
|
For example,
./lbrynet claim search --text="(\"silver\" + bitten)"
finally returns after the 5th try for me.
The text was updated successfully, but these errors were encountered: