Keith Turner created ACCUMULO-4832:
--------------------------------------

             Summary: Seeing warnings when write ahead log changes.
                 Key: ACCUMULO-4832
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4832
             Project: Accumulo
          Issue Type: Bug
            Reporter: Keith Turner


While running continuous ingest against 1.7.4-rc0 I saw a lot of warning like 
the followng.

{noformat}
2018-02-26 17:51:58,189 [log.TabletServerLogger] WARN : Logs closed while 
writing, retrying attempt 1 (suppressing retry messages for 180000ms)
2018-02-26 17:51:58,724 [log.TabletServerLogger] WARN : Logs closed while 
writing, retrying attempt 1 (suppressing retry messages for 180000ms)
2018-02-26 17:51:58,940 [log.TabletServerLogger] WARN : Logs closed while 
writing, retrying attempt 1 (suppressing retry messages for 180000ms)
2018-02-26 17:51:59,226 [log.TabletServerLogger] WARN : Logs closed while 
writing, retrying attempt 1 (suppressing retry messages for 180000ms)
2018-02-26 17:51:59,227 [log.TabletServerLogger] WARN : Logs closed while 
writing, retrying attempt 1 (suppressing retry messages for 180000ms)
2018-02-26 17:51:59,227 [log.TabletServerLogger] WARN : Logs closed while 
writing, retrying attempt 1 (suppressing retry messages for 180000ms)
{noformat}
 
The warning are generated by [TabletServerLogger.java line 
341|https://github.com/apache/accumulo/blob/4e91215f101362ef206e9f213b4d8d12b3f6e0e2/server/tserver/src/main/java/org/apache/accumulo/tserver/log/TabletServerLogger.java#L341]
 when a write ahead log is closed.  Write ahead logs are closed as part of 
normal operations as seen on [TabletServerLogger.java line 
386|https://github.com/apache/accumulo/blob/4e91215f101362ef206e9f213b4d8d12b3f6e0e2/server/tserver/src/main/java/org/apache/accumulo/tserver/log/TabletServerLogger.java#L386].
  There should not be a warning when this happens.  This is caused by changes 
made for ACCUMULO-4777.  Before these changes this event was logged at debug.  
At this time, these changes have not been released. It would be nice to fix 
this before releasing 1.7.4



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to