Notification logs are too verbose

Description

MDSNotificationFeedStore#85 logs an exception with the full stack trace when dataset service is unavailable. This keeps happening every second, so it is difficult to debug and find out why dataset service is not up. Maybe move the log message to debug? Or just have the message and move the exception to trace?

Release Notes

None

Activity

Show:
Bhooshan Mogal
February 24, 2015, 5:24 AM

Also found the same at DistributedStreamService where it catches a NotificationException and logs the entire exception.

We could potentially use this pattern from DefaultMetricDatasetFactory to retry until dataset service is up too:

Julien Guery
February 24, 2015, 12:09 PM

Ok I will use that same pattern.

Julien Guery
February 24, 2015, 5:05 PM
Fixed

Assignee

Julien Guery

Reporter

Bhooshan Mogal

Labels

None

Docs Impact

None

UX Impact

None

Components

Fix versions

Affects versions

Priority

Major