[
https://issues.apache.org/jira/browse/ACCUMULO-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Tubbs resolved ACCUMULO-3345.
-----------------------------------------
Resolution: Abandoned
Closing this stale issue. If this is still a problem, please create a new issue
or PR at https://github.com/apache/accumulo
> Redundant logging on failed multi-scans
> ---------------------------------------
>
> Key: ACCUMULO-3345
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3345
> Project: Accumulo
> Issue Type: Improvement
> Components: tserver
> Reporter: John Vines
> Priority: Major
>
> When a multi scan fails, for whatever reason, it gets double logged. This
> makes it harder to track down. We should settle on the logging coming from
> one location.
> The locations in question are-
> TabletServer.LookupTask.run, there's a catch Throwable that log.warns
> "exception while doing multi-scan " with the exception.
> Then higher in the stack under
> TabletServer.ThriftClientHandler.continueMultiScan, there's another catch
> Throwable that log.warns "Failed to get multiscan result"
> Then higher in the stack under thrift in
> ProcessFunction.process, there is another catch Throwable. This log.error
> "internal error processing *" and logs the exception.
> We should
> A. settle on multi-scan or multiscan or something else
> B. decide which one we prefer
> C. remove/mute the other ones in our default logging configuration
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
