milleruntime commented on issue #2544:
URL: https://github.com/apache/accumulo/issues/2544#issuecomment-1061906696
OK I think I know what is going on. Steps to reproduce (still not sure if
there is a bug though)
1. Create CI table with SlowIterator configured on MajC and test jar copied
into accumulo lib
2. Ingest some data (enough to trigger system compact)
3. From the shell, run `compact -t ci`
4. Run `listcompactions` to see that there are only system compactions
running
5. Run `fate print` to see the fate TX has started for the user compaction
CI table config:
<pre>
tserver.compaction.major.service.cs1.planner.opts.executors=[{"name":"small","type":"internal","maxSize":"16M","numThreads":8},{"name":"medium","type":"internal","maxSize":"128M","numThreads":4},{"name":"large","type":"internal","numThreads":2}]
table | table.iterator.majc.slow .................. |
1,org.apache.accumulo.test.functional.SlowIterator
table | table.iterator.majc.slow.opt.sleepTime .... | 5
</pre>
Each of the 2 tservers has 10 MajC compactions running on each, with 8
queued each (according to the Monitor). But its more like 24 according to
`listcompactions` and the logs.
<pre>
10:27:46 {test-jar} ~/workspace/uno/install/logs/accumulo$ grep
"tablet.files" *.log | grep "Compacting 1" | grep small | wc -l
16
10:27:59 {test-jar} ~/workspace/uno/install/logs/accumulo$ grep
"tablet.files" *.log | grep "Compacting 1" | grep medium | wc -l
8
</pre>
So it looks like the user compaction gets thrown in the pot with all of the
waiting system compactions.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@accumulo.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
