Github user arielvalentin commented on the pull request:
https://github.com/apache/accumulo/pull/18#issuecomment-62402671
@joshelser I agree that because the client may recover from the is strictly
not an error case, however I feel it is good to have breadcrumbs available when
trying to track down problems. In my specific case we run into some really slow
scans/writes and I don't know what the root cause is because I am not logging
at debug level. I look at the monitor UI and Accumulo is humming along but then
have to bump the client side log level in order to see that the first attempt
fails on every scan but the second attempt works just fine.
I find that the client side logging of first attempt failures at warn
level, as opposed to debug, to be very helpful because it allows our monitoring
tools to alert our administrators that our application may be having
connectivity issues. That allows them the ability to write reports and see how
often these failures occur and potentially track down the root cause.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
