[
https://issues.apache.org/jira/browse/KUDU-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17516304#comment-17516304
]
YifanZhang commented on KUDU-3354:
----------------------------------
{code:java}
I0221 04:22:12.031422 8866 maintenance_manager.cc:382] P
c4e995dc9e264d6fbcd01aacff4212bd: Scheduling
CompactRowSetsOp(64bf8251dd594197b493a8a5cd2e3e9c): perf
score=1279494840443460300019357683777979923760955028182284084266695498710755807790412216956702667800111812783791998911358244116400294695993868288.000000
I0221 04:22:12.032940 8806 tablet.cc:1898] T 64bf8251dd594197b493a8a5cd2e3e9c
P c4e995dc9e264d6fbcd01aacff4212bd: Compaction resulted in no output rows (all
input rows were GCed!) Removing all input rowsets. {code}
Seems that the maintenance manager sometimes schedule strange compact ops as
shown in the above log, these ops block flush ops because in the test tserver
is configured with '--maintenance_manager_num_threads=1'(the default value).
> Flaky test:
> DisableWriteWhenExceedingQuotaTest.TestDisableWritePrivilegeWhenExceedingSizeQuota
> ----------------------------------------------------------------------------------------------
>
> Key: KUDU-3354
> URL: https://issues.apache.org/jira/browse/KUDU-3354
> Project: Kudu
> Issue Type: Bug
> Reporter: YifanZhang
> Priority: Major
> Attachments: write_limit-itest.txt
>
>
> The test
> `DisableWriteWhenExceedingQuotaTest.TestDisableWritePrivilegeWhenExceedingSizeQuota`
> sometimes fails (at least in debug mode). The output is:
> /home/jenkins-slave/workspace/kudu-master/0/src/kudu/integration-tests/write_limit-itest.cc:229:
> Failure
> Value of: s.IsIOError()
> Actual: false
> Expected: true
> OK
> /home/jenkins-slave/workspace/kudu-master/0/src/kudu/integration-tests/write_limit-itest.cc:429:
> Failure
> Expected: TestSizeLimit() doesn't generate new fatal failures in the current
> thread.
> Actual: it does.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
