[ 
https://issues.apache.org/jira/browse/KUDU-2665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adar Dembo reopened KUDU-2665:
------------------------------
      Assignee: HeLifu  (was: Adar Dembo)

Reopening because another major source of flakiness has emerged. The test is 
now failing with error:
{noformat}
block_manager-stress-test.cc:399] Check failed: _s.ok() Bad status: Not found: 
Can't find block: 18425938387067637933
    @       0x3987e32625 __GI_raise at ??:0
    @       0x3987e33e05 __GI_abort at ??:0
    @           0x528b60 kudu::fs::BlockManagerStressTest<>::ReaderThread() at 
/data/somelongdirectorytoavoidrpathissues/src/kudu/thirdparty/installed/uninstrumented/include/glog/logging.h:717
    @           0x680f01 kudu::Thread::SuperviseThread() at 
/usr/include/pthread.h:545
    @       0x39882079d1 start_thread at ??:0
    @       0x3987ee88fd clone at ??:0
{noformat}

> BlockManagerStressTest.StressTest is extremely flaky
> ----------------------------------------------------
>
>                 Key: KUDU-2665
>                 URL: https://issues.apache.org/jira/browse/KUDU-2665
>             Project: Kudu
>          Issue Type: New Feature
>          Components: fs
>    Affects Versions: 1.9.0
>            Reporter: Mike Percy
>            Assignee: HeLifu
>            Priority: Major
>             Fix For: 1.9.0
>
>
> After some recent block manager changes the Block Manager Stress Test is 
> about 50% flaky on certain precommit builds. The failure looks like this:
> {code:java}
> /data/somelongdirectorytoavoidrpathissues/src/kudu/src/kudu/fs/block_manager-stress-test.cc:518:
>  Failure
> Failed
> Bad status: Not found: 
> /data/somelongdirectorytoavoidrpathissues/src/kudutest/block_manager-stress-test.0.BlockManagerStressTest_1.StressTest.1547778831841692-23619/data/e8ab31ef3e2143a5bc6d7a2b40e7805b.data:
>  No such file or directory (error 2)
> /data/somelongdirectorytoavoidrpathissues/src/kudu/src/kudu/fs/block_manager-stress-test.cc:549:
>  Failure
> Expected: this->InjectNonFatalInconsistencies() doesn't generate new fatal 
> failures in the current thread.
>  Actual: it does.
> {code}



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

Reply via email to