[
https://issues.apache.org/jira/browse/ACCUMULO-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser resolved ACCUMULO-3347.
----------------------------------
Resolution: Fixed
Added some basic logging (user, client and idle/lack-of-access time) to the
automatic sweep of sessions and when a TimeOutException is caught.
> Improve logging for cancelled scans
> -----------------------------------
>
> Key: ACCUMULO-3347
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3347
> Project: Accumulo
> Issue Type: Improvement
> Components: tserver
> Affects Versions: 1.5.2, 1.6.1
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: 1.6.2, 1.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The TabletServer watches the active scans presently running and "stops" any
> that have not had any client communication in the time set by
> {{Property.TSERV_SESSION_MAXIDLE}}.
> The SessionManager reads the last accessed time for each Session (which is
> updated by the Thrift RPC implementation). When the SessionManager finds a
> Session which hasn't been updated within the required time limit, it calls
> cleanup on the Session (which ultimately calls cancel on the ScanTask inside
> of the Session) and removes it from its internal state.
> Presently, there is absolutely no logging on the server side when this occurs
> which would make it very difficult, if not impossible, to debug this
> situation and determine that TServer reaped the Session because it was
> inactive.
> We should, at a minimum, have logging so that someone debugging the system
> for a Session that was closed could validate that it was expected system
> functionality.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
