[
https://issues.apache.org/jira/browse/KUDU-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17868754#comment-17868754
]
ASF subversion and git services commented on KUDU-3597:
-------------------------------------------------------
Commit 315942c8eb61223269cae25f4e5e40c9e57dca0a in kudu's branch
refs/heads/master from Alexey Serbin
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=315942c8e ]
[tests] more robust TabletServerDiskErrorITest::SetUp()
This patch adds the verification for the status of AddTabletServer()
call in TabletServerDiskErrorITest::SetUp().
The motivation for this patch is KUDU-3597.
This is a follow-up to cf6927cb153f384afb649b664de1d4276bd6d83f.
Change-Id: I192a05bee4bfadddf2a3237f25dc17882cae1dc2
Reviewed-on: http://gerrit.cloudera.org:8080/21614
Tested-by: Kudu Jenkins
Reviewed-by: Abhishek Chennaka <[email protected]>
> Test scenarios of TabletServerDiskErrorITest fail from time to time
> -------------------------------------------------------------------
>
> Key: KUDU-3597
> URL: https://issues.apache.org/jira/browse/KUDU-3597
> Project: Kudu
> Issue Type: Bug
> Components: test
> Affects Versions: 1.17.0
> Reporter: Alexey Serbin
> Priority: Major
> Attachments: disk_failure-itest.txt.xz
>
>
> Test scenarios in TabletServerDiskErrorITest fail from time to time. For
> example,
> {{TabletServerDiskError/TabletServerDiskErrorITest.TestSpaceAvailableMetrics}}
> test scenario sometimes fails with errors like below (at least in TSAN
> builds). The full log is attached.
> TabletServerDiskErrorITest
> {noformat}
> src/kudu/integration-tests/disk_failure-itest.cc:267: Failure
> Failed
> Bad status: Network error: rpc failed: Client connection negotiation failed:
> client connection to 127.21.83.1:33163: connect: Connection refused (error
> 111)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
