You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2014/11/19 22:15:33 UTC
[jira] [Created] (ACCUMULO-3347) Improve logging for cancelled
scans
Josh Elser created ACCUMULO-3347:
------------------------------------
Summary: 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.6.1, 1.5.2
Reporter: Josh Elser
Assignee: Josh Elser
Fix For: 1.6.2, 1.7.0
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)