You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by GitBox <gi...@apache.org> on 2018/06/29 21:28:15 UTC
[GitHub] keith-turner commented on issue #545: fixes #543 Avoid logLock when
determining WALs in use
keith-turner commented on issue #545: fixes #543 Avoid logLock when determining WALs in use
URL: https://github.com/apache/accumulo/pull/545#issuecomment-401478685
I ran WriteAheadLogIT and looked at the debug logs to see if this change was working as expected. Saw the following which showed the set operations were working as expected.
```
2018-06-29 16:39:25,397 [tablet.Tablet] DEBUG: Logs for memory compacted: 1<< 38577b31-28a0-46d8-9467-84d2952e1d17
2018-06-29 16:39:25,398 [tablet.Tablet] DEBUG: Logs for memory compacted: 1<< 697f2016-6e73-454b-b550-1d882272c520
2018-06-29 16:39:25,398 [tablet.Tablet] DEBUG: Logs for memory compacted: 1<< ad2640e2-001a-4835-b2a2-5bbcc9eeb374
2018-06-29 16:39:25,398 [tablet.Tablet] DEBUG: Logs for current memory: 1<< 697f2016-6e73-454b-b550-1d882272c520
2018-06-29 16:39:25,398 [tablet.Tablet] DEBUG: Logs to be destroyed: 1<< 38577b31-28a0-46d8-9467-84d2952e1d17
2018-06-29 16:39:25,398 [tablet.Tablet] DEBUG: Logs to be destroyed: 1<< ad2640e2-001a-4835-b2a2-5bbcc9eeb374
```
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services