Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
None
-
None
-
None
-
None
Description
I'd like to propose we have a standard interface for hadoop components, the things that get started or stopped when you bring up a namenode. currently, some of these classes have a stop() or shutdown() method, with no standard name/interface, but no way of seeing if they are live, checking their health of shutting them down reliably. Indeed, there is a tendency for the spawned threads to not want to die; to require the entire process to be killed to stop the workers.
Having a standard interface would make it easier for
- management tools to manage the different things
- monitoring the state of things
- subclassing
The latter is interesting as right now TaskTracker and JobTracker start up threads in their constructor; that's very dangerous as subclasses may have their methods called before they are full initialised. Adding this interface would be the right time to clean up the startup process so that subclassing is less risky.
Attachments
Attachments
Issue Links
- blocks
-
MAPREDUCE-213 Provide a way to query job tracker about its daemon thread's status
- Resolved
- depends upon
-
HADOOP-5348 Create a ThrowableWritable for serializing exceptions robustly
- Resolved
-
HADOOP-3642 add a HadoopIOException that can be thrown in any method that has IOException on its signature
- Closed
-
HADOOP-4059 Add tests that try starting the various hadoop command line scripts
- Resolved
- incorporates
-
HADOOP-3415 JobEndNotifier isnt synchronized, doesnt check state before acting
- Closed
-
HADOOP-6194 Add service base class and tests to hadoop-common/util
- Resolved
- is depended upon by
-
HDFS-239 Brief, baseline namenode health check
- Open
-
HADOOP-3969 Provide Mechanism to optionally expose public org.apache.hadoop.util.Services APIs
- Resolved
-
MAPREDUCE-233 Integrate TaskTracker with the Service base class
- Resolved
- relates to
-
HADOOP-6915 Add daemon restart option
- Open