[
https://issues.apache.org/jira/browse/HADOOP-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley updated HADOOP-1429:
----------------------------------
Status: Open (was: Patch Available)
I don't think this is a good way of dealing with it. I'd prefer that we catch
InterruptedException at the top level, not print anything, and exit the thread.
Ignoring InterruptedException is a bad practice that we will need to clean up
at some point.
> RPC Server won't go quietly
> ---------------------------
>
> Key: HADOOP-1429
> URL: https://issues.apache.org/jira/browse/HADOOP-1429
> Project: Hadoop
> Issue Type: Improvement
> Components: ipc
> Reporter: stack
> Assigned To: stack
> Priority: Minor
> Attachments: noisyshutdown.patch, noisyshutdown.patch
>
>
> Trying to do a controlled shutdown of hbase, the RPC Server spews the
> following ugly output:
> unknown-208-76-47-46:~/Documents/checkouts/hadoop-trunk stack$
> ./src/contrib/hbase/bin/hbase master stop
> 07/05/24 12:53:47 INFO ipc.Server: Stopping server on 60000
> 07/05/24 12:53:47 INFO ipc.Server: IPC Server handler 0 on 60000 caught:
> java.lang.InterruptedException
> java.lang.InterruptedException
> at java.lang.Object.wait(Native Method)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:541)
> 07/05/24 12:53:47 INFO ipc.Server: IPC Server handler 0 on 60000: exiting
> unknown-208-76-47-46:~/Documents/checkouts/hadoop-trunk stack$ 07/05/24
> 12:53:47 INFO ipc.Server: IPC Server handler 1 on 600
> 00 caught: java.lang.InterruptedException
> java.lang.InterruptedException
> at java.lang.Object.wait(Native Method)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:541)
> 07/05/24 12:53:47 INFO ipc.Server: IPC Server handler 2 on 60000 caught:
> java.lang.InterruptedException
> java.lang.InterruptedException
> at java.lang.Object.wait(Native Method)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:541)
> ...
> You get the same noise when if run the TestIPC unit test.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
