milleruntime commented on pull request #2215:
URL: https://github.com/apache/accumulo/pull/2215#issuecomment-1059341120
While testing with Uno and the `SlowIterator`, I noticed that multiple FATE
Txs get kicked off if you issue multiple compact commands. This may be
unrelated to your changes but I think it is noteworthy. I thought there were
checks that prevent another compaction from running if the table doesn't need
to be compacted. It could be that the check for this happens in CompactRange,
after the FATE Tx gets started.
<pre>
root@uno> fate print
txid: 1bc091ffb9162774 status: IN_PROGRESS op: CompactRange
locked: [R:+default, R:1] locking: [] top: CompactionDriver
created: 2022-03-04T16:38:44.088Z
txid: 543834dd76654bc1 status: IN_PROGRESS op: CompactRange
locked: [R:+default, R:1] locking: [] top: CompactionDriver
created: 2022-03-04T16:56:29.574Z
txid: 7e20a7508cac33d9 status: IN_PROGRESS op: CompactRange
locked: [R:+default, R:1] locking: [] top: CompactionDriver
created: 2022-03-04T16:57:25.536Z
txid: 1ca0ac1b2198cfe0 status: IN_PROGRESS op: CompactRange
locked: [R:+default, R:1] locking: [] top: CompactionDriver
created: 2022-03-04T16:38:17.825Z
4 transactions
root@uno> listcompactions
SERVER | AGE | TYPE | REASON | READ | WROTE | TABLE
| TABLET | INPUT | OUTPUT
| ITERATORS | ITERATOR OPTIONS
ip-10-113-12-25:10000 | 19m15s | FULL | USER | 224K | 224K |
ci | 1<< | 3 |
/1/default_tablet/A000005e.rf_tmp | [] | {}
</pre>
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
