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 2008/04/18 23:30:21 UTC
[jira] Created: (HADOOP-3282) TestCheckpoint occasionally fails
because of the port issues.
TestCheckpoint occasionally fails because of the port issues.
-------------------------------------------------------------
Key: HADOOP-3282
URL: https://issues.apache.org/jira/browse/HADOOP-3282
Project: Hadoop Core
Issue Type: Bug
Components: test
Affects Versions: 0.17.0
Reporter: Konstantin Shvachko
Assignee: Konstantin Shvachko
Fix For: 0.18.0
This is related to timing issues. If MiniDFSCluster does not stop fast enough the name-node won't start because the port is busy.
So the tests should reset the configuration port properties before each server startup, because servers change those values to the actual port numbers they run.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-3282) TestCheckpoint occasionally fails
because of the port issues.
Posted by "Konstantin Shvachko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Shvachko updated HADOOP-3282:
----------------------------------------
Status: Patch Available (was: Open)
> TestCheckpoint occasionally fails because of the port issues.
> -------------------------------------------------------------
>
> Key: HADOOP-3282
> URL: https://issues.apache.org/jira/browse/HADOOP-3282
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.17.0
> Reporter: Konstantin Shvachko
> Assignee: Konstantin Shvachko
> Fix For: 0.18.0
>
> Attachments: TestCheckpointPorts.patch
>
>
> This is related to timing issues. If MiniDFSCluster does not stop fast enough the name-node won't start because the port is busy.
> So the tests should reset the configuration port properties before each server startup, because servers change those values to the actual port numbers they run.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-3282) TestCheckpoint occasionally fails
because of the port issues.
Posted by "Konstantin Shvachko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Shvachko updated HADOOP-3282:
----------------------------------------
Attachment: TestCheckpointPorts.patch
I wrapped all startup calls for name- and secondary nodes, and uniformly set ports to 0 rather than setting it individually before each call.
> TestCheckpoint occasionally fails because of the port issues.
> -------------------------------------------------------------
>
> Key: HADOOP-3282
> URL: https://issues.apache.org/jira/browse/HADOOP-3282
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.17.0
> Reporter: Konstantin Shvachko
> Assignee: Konstantin Shvachko
> Fix For: 0.18.0
>
> Attachments: TestCheckpointPorts.patch
>
>
> This is related to timing issues. If MiniDFSCluster does not stop fast enough the name-node won't start because the port is busy.
> So the tests should reset the configuration port properties before each server startup, because servers change those values to the actual port numbers they run.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-3282) TestCheckpoint occasionally fails
because of the port issues.
Posted by "Konstantin Shvachko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Shvachko updated HADOOP-3282:
----------------------------------------
Resolution: Fixed
Fix Version/s: (was: 0.17.0)
0.18.0
Status: Resolved (was: Patch Available)
I just committed this.
> TestCheckpoint occasionally fails because of the port issues.
> -------------------------------------------------------------
>
> Key: HADOOP-3282
> URL: https://issues.apache.org/jira/browse/HADOOP-3282
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.17.0
> Reporter: Konstantin Shvachko
> Assignee: Konstantin Shvachko
> Fix For: 0.18.0
>
> Attachments: TestCheckpointPorts.patch
>
>
> This is related to timing issues. If MiniDFSCluster does not stop fast enough the name-node won't start because the port is busy.
> So the tests should reset the configuration port properties before each server startup, because servers change those values to the actual port numbers they run.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-3282) TestCheckpoint occasionally fails
because of the port issues.
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591371#action_12591371 ]
Hudson commented on HADOOP-3282:
--------------------------------
Integrated in Hadoop-trunk #467 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/467/])
> TestCheckpoint occasionally fails because of the port issues.
> -------------------------------------------------------------
>
> Key: HADOOP-3282
> URL: https://issues.apache.org/jira/browse/HADOOP-3282
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.17.0
> Reporter: Konstantin Shvachko
> Assignee: Konstantin Shvachko
> Fix For: 0.18.0
>
> Attachments: TestCheckpointPorts.patch
>
>
> This is related to timing issues. If MiniDFSCluster does not stop fast enough the name-node won't start because the port is busy.
> So the tests should reset the configuration port properties before each server startup, because servers change those values to the actual port numbers they run.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-3282) TestCheckpoint occasionally fails
because of the port issues.
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590805#action_12590805 ]
Hadoop QA commented on HADOOP-3282:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12380542/TestCheckpointPorts.patch
against trunk revision 645773.
@author +1. The patch does not contain any @author tags.
tests included +1. The patch appears to include 3 new or modified tests.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new javac compiler warnings.
release audit +1. The applied patch does not generate any new release audit warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests +1. The patch passed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2285/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2285/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2285/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2285/console
This message is automatically generated.
> TestCheckpoint occasionally fails because of the port issues.
> -------------------------------------------------------------
>
> Key: HADOOP-3282
> URL: https://issues.apache.org/jira/browse/HADOOP-3282
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.17.0
> Reporter: Konstantin Shvachko
> Assignee: Konstantin Shvachko
> Fix For: 0.18.0
>
> Attachments: TestCheckpointPorts.patch
>
>
> This is related to timing issues. If MiniDFSCluster does not stop fast enough the name-node won't start because the port is busy.
> So the tests should reset the configuration port properties before each server startup, because servers change those values to the actual port numbers they run.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-3282) TestCheckpoint occasionally fails
because of the port issues.
Posted by "Konstantin Shvachko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Shvachko updated HADOOP-3282:
----------------------------------------
Affects Version/s: (was: 0.17.0)
0.18.0
> TestCheckpoint occasionally fails because of the port issues.
> -------------------------------------------------------------
>
> Key: HADOOP-3282
> URL: https://issues.apache.org/jira/browse/HADOOP-3282
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.18.0
> Reporter: Konstantin Shvachko
> Assignee: Konstantin Shvachko
> Fix For: 0.18.0
>
> Attachments: TestCheckpointPorts.patch
>
>
> This is related to timing issues. If MiniDFSCluster does not stop fast enough the name-node won't start because the port is busy.
> So the tests should reset the configuration port properties before each server startup, because servers change those values to the actual port numbers they run.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-3282) TestCheckpoint occasionally fails
because of the port issues.
Posted by "Nigel Daley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nigel Daley updated HADOOP-3282:
--------------------------------
Fix Version/s: (was: 0.18.0)
0.17.0
> TestCheckpoint occasionally fails because of the port issues.
> -------------------------------------------------------------
>
> Key: HADOOP-3282
> URL: https://issues.apache.org/jira/browse/HADOOP-3282
> Project: Hadoop Core
> Issue Type: Bug
> Components: test
> Affects Versions: 0.17.0
> Reporter: Konstantin Shvachko
> Assignee: Konstantin Shvachko
> Fix For: 0.17.0
>
> Attachments: TestCheckpointPorts.patch
>
>
> This is related to timing issues. If MiniDFSCluster does not stop fast enough the name-node won't start because the port is busy.
> So the tests should reset the configuration port properties before each server startup, because servers change those values to the actual port numbers they run.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.