-
Notifications
You must be signed in to change notification settings - Fork 25k
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
TransportException when calling _snapshot/repo/_all
on non-master
#26906
Comments
_snapshot/repo/_all
on non-master_snapshot/repo/_all
on non-master
The node 10.200.7.5 will hopefully have a stack trace in its logs. If so, can you share it here? If not, can you send the request again with the URL parameter |
No stack trace on the master node, here's the error_trace
|
My guess is this is because of the sheer size of the response body (over 10 million characters) |
I think that you're encountering a bug fixed by #26127 |
Closed by #26127 |
Elasticsearch version :
Version: 5.4.3, Build: eed30a8/2017-06-22T00:34:03.743Z, JVM: 1.8.0_131
Plugins installed: s3-repository
JVM version:
OS version:
Linux ip-10-200-7-5 4.4.0-1020-aws #29-Ubuntu SMP Wed Jun 14 15:54:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Description of the problem including expected versus actual behavior:
Executing
curl localhost:9200/_snapshot/prod/_all
on a non-master node results in:Expected it to return all snapshots. When run against the master node this returns fine.
Steps to reproduce:
Create an s3 repository.
Fill it with some 250 snapshots, each containing ~2,000 indices.
Attempt to call
_snapshot/repository_name/_all
on a non-master nodeProvide logs (if relevant):
The text was updated successfully, but these errors were encountered: