Adar Dembo has posted comments on this change. ( http://gerrit.cloudera.org:8080/10473 )
Change subject: WIP: KUDU-2450. Retry on EAGAIN on create / destroy mutex ...................................................................... Patch Set 1: (1 comment) http://gerrit.cloudera.org:8080/#/c/10473/1//COMMIT_MSG Commit Message: http://gerrit.cloudera.org:8080/#/c/10473/1//COMMIT_MSG@7 PS1, Line 7: WIP: KUDU-2450. Retry on EAGAIN on create / destroy mutex KUDU-2450 shows EBUSY, not EAGAIN. The actual error code was 16 (Device or resource busy). From /usr/include/asm-generic/errno-base.h: #define EBUSY 16 /* Device or resource busy */ As for why it's happening, the manpage for pthread_mutex_destroy says: The pthread_mutex_destroy function returns the following error code on error: EBUSY the mutex is currently locked. So it sounds like ThreadMgr had the mutex locked at the time that it was destroyed? -- To view, visit http://gerrit.cloudera.org:8080/10473 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-Project: kudu Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: Idb865c2e31d83eb7897f44ac414c23baaa7cbed5 Gerrit-Change-Number: 10473 Gerrit-PatchSet: 1 Gerrit-Owner: Mike Percy <[email protected]> Gerrit-Reviewer: Adar Dembo <[email protected]> Gerrit-Reviewer: Kudu Jenkins Gerrit-Comment-Date: Tue, 22 May 2018 01:41:40 +0000 Gerrit-HasComments: Yes
