You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Konstantin Shvachko (JIRA)" <ji...@apache.org> on 2006/07/27 20:30:13 UTC
[jira] Created: (HADOOP-394) MiniDFSCluster shudown order
MiniDFSCluster shudown order
----------------------------
Key: HADOOP-394
URL: http://issues.apache.org/jira/browse/HADOOP-394
Project: Hadoop
Issue Type: Improvement
Components: dfs
Affects Versions: 0.4.0
Reporter: Konstantin Shvachko
Assigned To: Konstantin Shvachko
Priority: Minor
I propose to reverse the order of shutdown in MiniDFSCluster.
Currently it shutdowns the name node first and then the data node,
which causes the data node throwing unnecessary Exceptions in unit test.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Work started: (HADOOP-394) MiniDFSCluster shudown order
Posted by "Konstantin Shvachko (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-394?page=all ]
Work on HADOOP-394 started by Konstantin Shvachko.
> MiniDFSCluster shudown order
> ----------------------------
>
> Key: HADOOP-394
> URL: http://issues.apache.org/jira/browse/HADOOP-394
> Project: Hadoop
> Issue Type: Improvement
> Components: dfs
> Affects Versions: 0.4.0
> Reporter: Konstantin Shvachko
> Assigned To: Konstantin Shvachko
> Priority: Minor
> Attachments: MiniDFSClusterShutdownOrder.patch
>
>
> I propose to reverse the order of shutdown in MiniDFSCluster.
> Currently it shutdowns the name node first and then the data node,
> which causes the data node throwing unnecessary Exceptions in unit test.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HADOOP-394) MiniDFSCluster shudown order
Posted by "Konstantin Shvachko (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-394?page=comments#action_12428171 ]
Konstantin Shvachko commented on HADOOP-394:
--------------------------------------------
This is resolved. Patch was applied on 08/01/06.
> MiniDFSCluster shudown order
> ----------------------------
>
> Key: HADOOP-394
> URL: http://issues.apache.org/jira/browse/HADOOP-394
> Project: Hadoop
> Issue Type: Improvement
> Components: dfs
> Affects Versions: 0.4.0
> Reporter: Konstantin Shvachko
> Assigned To: Konstantin Shvachko
> Priority: Minor
> Attachments: MiniDFSClusterShutdownOrder.patch
>
>
> I propose to reverse the order of shutdown in MiniDFSCluster.
> Currently it shutdowns the name node first and then the data node,
> which causes the data node throwing unnecessary Exceptions in unit test.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (HADOOP-394) MiniDFSCluster shudown order
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-394?page=all ]
Doug Cutting resolved HADOOP-394.
---------------------------------
Fix Version/s: 0.5.0
Resolution: Fixed
Forgot to resolve this earlier. Thanks, Konstantin!
> MiniDFSCluster shudown order
> ----------------------------
>
> Key: HADOOP-394
> URL: http://issues.apache.org/jira/browse/HADOOP-394
> Project: Hadoop
> Issue Type: Improvement
> Components: dfs
> Affects Versions: 0.4.0
> Reporter: Konstantin Shvachko
> Assigned To: Konstantin Shvachko
> Priority: Minor
> Fix For: 0.5.0
>
> Attachments: MiniDFSClusterShutdownOrder.patch
>
>
> I propose to reverse the order of shutdown in MiniDFSCluster.
> Currently it shutdowns the name node first and then the data node,
> which causes the data node throwing unnecessary Exceptions in unit test.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HADOOP-394) MiniDFSCluster shudown order
Posted by "Konstantin Shvachko (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-394?page=all ]
Konstantin Shvachko updated HADOOP-394:
---------------------------------------
Attachment: MiniDFSClusterShutdownOrder.patch
With this patch the data node will shutdown before the name node.
> MiniDFSCluster shudown order
> ----------------------------
>
> Key: HADOOP-394
> URL: http://issues.apache.org/jira/browse/HADOOP-394
> Project: Hadoop
> Issue Type: Improvement
> Components: dfs
> Affects Versions: 0.4.0
> Reporter: Konstantin Shvachko
> Assigned To: Konstantin Shvachko
> Priority: Minor
> Attachments: MiniDFSClusterShutdownOrder.patch
>
>
> I propose to reverse the order of shutdown in MiniDFSCluster.
> Currently it shutdowns the name node first and then the data node,
> which causes the data node throwing unnecessary Exceptions in unit test.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira