Skip to content

Conversation

arp7
Copy link
Contributor

@arp7 arp7 commented Nov 16, 2016

Change-Id: I664e5c719921ef5e0891bc392f37ee67639a8660

Change-Id: I664e5c719921ef5e0891bc392f37ee67639a8660
}

if (storageLocationChecker != null) {
storageLocationChecker.shutdownAndWait(10, TimeUnit.SECONDS);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Something for you to consider, most of the other threads seems to shutdown much quicker, do we need to wait 10 seconds ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point. We can exit much quicker since a stalled disk check need not block shutdown at all. I'll change it to 1 second.

}

@Test(timeout = 30000)
public void testDataDirValidation() throws Throwable {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Presuming that we will have an equivalent or better test using storageLocationChecker ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes there's new tests in TestStorageLocationChecker added by HDFS-11119 which cover this better with different combinations of failed/healthy storages.

Copy link
Contributor

@anuengineer anuengineer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1, pending Jenkins and if you think 10 seconds for the datanode shutdown is ok.

@anuengineer
Copy link
Contributor

Arpit, thanks for updating the patch. +1. LGTM.

@aajisaka
Copy link
Member

aajisaka commented Jul 26, 2019

This issue has been fixed. Closing this PR as well.

@aajisaka aajisaka closed this Jul 26, 2019
shanthoosh pushed a commit to shanthoosh/hadoop that referenced this pull request Oct 15, 2019
This is not the solution posted in SAMZA-1228. For now, we are moving jmxserver lifecycle to be within the container. Ideally, it should be within the Streamprocessor so that the job coordinator can also be associated with the same instance.

Author: Navina Ramesh <navina@apache.org>

Reviewers: Xinyu Liu <xiliu@linkedin.com>, Prateek Maheshwari <pmaheshw@linkedin.com>

Closes apache#162 from navina/SAMZA-1228
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants