| commit | 6c07e5d657389ccaea458978975df3e0380a1b44 | |
| author | Arunachalam Thirupathi <arunachalam.t@gmail.com> | |
| Tue, 18 Feb 2014 21:21:15 +0000 (18 13:21 -0800) | ||
| committer | Arunachalam Thirupathi <arunachalam.t@gmail.com> | |
| Thu, 20 Feb 2014 19:08:19 +0000 (20 11:08 -0800) | ||
| tree | b67e1503d34d658921ac4e063bc34854b5ff5939 | treesnapshot (tar.gz zip) |
| parent | c443c10091ef33d37f22ad57364d7f33f9e5cee1 | commitdiff |
Cleanup expected exception stack trace in logs
1) Expected exception stack trace is logged at warning level.
This causes the monitoring system(EKG) to pickup these stack traces.
Do not log these stack trace unless debug is enabled or if the
exception has inner exception
2) When a node is unavailable in the resource pool map, ignore the
cleanup. This can happen because the resource pool map used by
the failure detector and the other requests are different.
1) Expected exception stack trace is logged at warning level.
This causes the monitoring system(EKG) to pickup these stack traces.
Do not log these stack trace unless debug is enabled or if the
exception has inner exception
2) When a node is unavailable in the resource pool map, ignore the
cleanup. This can happen because the resource pool map used by
the failure detector and the other requests are different.
| src/java/voldemort/store/routed/action/AbstractAction.java | diffblobblamehistory | |
| src/java/voldemort/utils/pool/KeyedResourcePool.java | diffblobblamehistory |