Skip to content
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

Repository verification exceptions should be logged #11760

Closed
imotov opened this Issue Jun 18, 2015 · 0 comments

Comments

Projects
None yet
1 participant
@imotov
Copy link
Member

commented Jun 18, 2015

Currently repository verification exceptions are returned to the user, but not logged on the node where the exception occurred. This behavior makes debugging of some repository registration issues difficult. See elastic/elasticsearch-cloud-aws#217 for example.

@imotov imotov self-assigned this Jun 18, 2015

imotov added a commit to imotov/elasticsearch that referenced this issue Jun 20, 2015

Improve logging of repository verification exceptions.
Some repository verification exceptions are currently only returned to the users but not logged on the nodes where the exceptions occurred, which makes troubleshooting difficult.

Closes elastic#11760

imotov added a commit that referenced this issue Jun 20, 2015

Improve logging of repository verification exceptions.
Some repository verification exceptions are currently only returned to the users but not logged on the nodes where the exceptions occurred, which makes troubleshooting difficult.

Closes #11760

imotov added a commit that referenced this issue Jun 20, 2015

Improve logging of repository verification exceptions.
Some repository verification exceptions are currently only returned to the users but not logged on the nodes where the exceptions occurred, which makes troubleshooting difficult.

Closes #11760
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.