Logging exceptions at DEBUG?


(Otis Gospodnetić) #1

Hello,

I'm trying to investigate some ES errors and when I look at the logs I see
things like this:

[2012-06-20 12:07:53,367][DEBUG][action.search.type ] [Foo search 1]
[48639] Failed to execute fetch phase
org.elasticsearch.transport.RemoteTransportException: [Foo search
4][inet[/123.37.47.62:9300]][search/phase/fetch/id]
Caused by: org.elasticsearch.search.SearchContextMissingException: No
search context found for id [48639]

Why is this at DEBUG level and not ERROR? Shouldn't this be ERROR? I'll
happily open an issue.

Thanks,
Otis

Search Analytics - http://sematext.com/search-analytics/index.html
Scalable Performance Monitoring - http://sematext.com/spm/index.html


(Shay Banon) #2

Its by design. Action failures are propagated back to the user, so we don't
log them as errors.

On Wed, Jun 20, 2012 at 6:11 PM, Otis Gospodnetic <
otis.gospodnetic@gmail.com> wrote:

Hello,

I'm trying to investigate some ES errors and when I look at the logs I see
things like this:

[2012-06-20 12:07:53,367][DEBUG][action.search.type ] [Foo search 1]
[48639] Failed to execute fetch phase
org.elasticsearch.transport.RemoteTransportException: [Foo search
4][inet[/123.37.47.62:9300]][search/phase/fetch/id]
Caused by: org.elasticsearch.search.SearchContextMissingException: No
search context found for id [48639]

Why is this at DEBUG level and not ERROR? Shouldn't this be ERROR? I'll
happily open an issue.

Thanks,
Otis

Search Analytics - http://sematext.com/search-analytics/index.html
Scalable Performance Monitoring - http://sematext.com/spm/index.html


(system) #3