big-data/hadoop
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

HADOOP-11333. Fix deadlock in DomainSocketWatcher when the notification pipe is full (zhaoyunjiong via cmccabe)

Browse Source
This commit is contained in:
Colin Patrick Mccabe 2014-12-01 11:42:10 -08:00
parent c732ed760e
commit 86e3993def
2 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
hadoop-common-project/hadoop-common/CHANGES.txt
View File

@ -473,6 +473,9 @@ Release 2.7.0 - UNRELEASED
HADOOP-11300. KMS startup scripts must not display the keystore /
truststore passwords. (Arun Suresh via wang)
HADOOP-11333. Fix deadlock in DomainSocketWatcher when the notification
pipe is full (zhaoyunjiong via cmccabe)
Release 2.6.0 - 2014-11-18
INCOMPATIBLE CHANGES

15
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/net/unix/DomainSocketWatcher.java
View File

@ -103,6 +103,7 @@ private class NotificationHandler implements Handler {
public boolean handle(DomainSocket sock) {
assert(lock.isHeldByCurrentThread());
try {
kicked = false;
if (LOG.isTraceEnabled()) {
LOG.trace(this + ": NotificationHandler: doing a read on " +
sock.fd);
@ -228,6 +229,14 @@ private static class FdSet {
* Whether or not this DomainSocketWatcher is closed.
*/
private boolean closed = false;
/**
* True if we have written a byte to the notification socket. We should not
* write anything else to the socket until the notification handler has had a
* chance to run. Otherwise, our thread might block, causing deadlock.
* See HADOOP-11333 for details.
*/
private boolean kicked = false;
public DomainSocketWatcher(int interruptCheckPeriodMs) throws IOException {
if (loadingFailureReason != null) {
@ -348,8 +357,14 @@ public void remove(DomainSocket sock) {
*/
private void kick() {
assert(lock.isHeldByCurrentThread());
if (kicked) {
return;
}
try {
notificationSockets[0].getOutputStream().write(0);
kicked = true;
} catch (IOException e) {
if (!closed) {
LOG.error(this + ": error writing to notificationSockets[0]", e);