[jira] [Updated] (HDFS-9740) Use a reasonable limit in DFSTestUtil.waitForMetric()
[
https://issues.apache.org/jira/browse/HDFS-9740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Junping Du updated HDFS-9740:
-
Fix Version/s: 2.8.0
> Use a reasonable limit in DFSTestUtil.waitForMetric()
> -
>
> Key: HDFS-9740
> URL: https://issues.apache.org/jira/browse/HDFS-9740
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
>Reporter: Kihwal Lee
>Assignee: Chang Li
> Fix For: 2.8.0, 2.7.3, 3.0.0-alpha1
>
> Attachments: HDFS-9740-branch-2.7.patch, HDFS-9740-branch-2.patch,
> HDFS-9740.patch
>
>
> If test is detecting a bug, it will probably hit the long surefire timeout
> because the max is {{Integer.MAX_VALUE}}. Use something more realistic. The
> default jmx update interval is 10 seconds, so something like 60 seconds
> should be more than enough.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-9740) Use a reasonable limit in DFSTestUtil.waitForMetric()
[
https://issues.apache.org/jira/browse/HDFS-9740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinayakumar B updated HDFS-9740:
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.7.3
Status: Resolved (was: Patch Available)
Committed to trunk, branch-2, branch-2.8 and branch-2.7
There were some line differences while cherry-picking to branch-2 and
branch-2.7. Resolved them. Will attach the committed patches.
Thanks [~lichangleo] and [~kihwal]
> Use a reasonable limit in DFSTestUtil.waitForMetric()
> -
>
> Key: HDFS-9740
> URL: https://issues.apache.org/jira/browse/HDFS-9740
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
>Reporter: Kihwal Lee
>Assignee: Chang Li
> Fix For: 2.7.3
>
> Attachments: HDFS-9740.patch
>
>
> If test is detecting a bug, it will probably hit the long surefire timeout
> because the max is {{Integer.MAX_VALUE}}. Use something more realistic. The
> default jmx update interval is 10 seconds, so something like 60 seconds
> should be more than enough.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HDFS-9740) Use a reasonable limit in DFSTestUtil.waitForMetric()
[
https://issues.apache.org/jira/browse/HDFS-9740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinayakumar B updated HDFS-9740:
Attachment: HDFS-9740-branch-2.7.patch
HDFS-9740-branch-2.patch
Branch-2 and branch-2.7 committed patches.
> Use a reasonable limit in DFSTestUtil.waitForMetric()
> -
>
> Key: HDFS-9740
> URL: https://issues.apache.org/jira/browse/HDFS-9740
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
>Reporter: Kihwal Lee
>Assignee: Chang Li
> Fix For: 2.7.3
>
> Attachments: HDFS-9740-branch-2.7.patch, HDFS-9740-branch-2.patch,
> HDFS-9740.patch
>
>
> If test is detecting a bug, it will probably hit the long surefire timeout
> because the max is {{Integer.MAX_VALUE}}. Use something more realistic. The
> default jmx update interval is 10 seconds, so something like 60 seconds
> should be more than enough.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HDFS-9740) Use a reasonable limit in DFSTestUtil.waitForMetric()
[
https://issues.apache.org/jira/browse/HDFS-9740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinayakumar B updated HDFS-9740:
Component/s: test
> Use a reasonable limit in DFSTestUtil.waitForMetric()
> -
>
> Key: HDFS-9740
> URL: https://issues.apache.org/jira/browse/HDFS-9740
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
>Reporter: Kihwal Lee
>Assignee: Chang Li
> Attachments: HDFS-9740.patch
>
>
> If test is detecting a bug, it will probably hit the long surefire timeout
> because the max is {{Integer.MAX_VALUE}}. Use something more realistic. The
> default jmx update interval is 10 seconds, so something like 60 seconds
> should be more than enough.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HDFS-9740) Use a reasonable limit in DFSTestUtil.waitForMetric()
[
https://issues.apache.org/jira/browse/HDFS-9740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chang Li updated HDFS-9740:
---
Status: Patch Available (was: Open)
[~kihwal] uploaded a patch to change wait time to 60 seconds
> Use a reasonable limit in DFSTestUtil.waitForMetric()
> -
>
> Key: HDFS-9740
> URL: https://issues.apache.org/jira/browse/HDFS-9740
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Kihwal Lee
>Assignee: Chang Li
> Attachments: HDFS-9740.patch
>
>
> If test is detecting a bug, it will probably hit the long surefire timeout
> because the max is {{Integer.MAX_VALUE}}. Use something more realistic. The
> default jmx update interval is 10 seconds, so something like 60 seconds
> should be more than enough.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HDFS-9740) Use a reasonable limit in DFSTestUtil.waitForMetric()
[
https://issues.apache.org/jira/browse/HDFS-9740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chang Li updated HDFS-9740:
---
Attachment: HDFS-9740.patch
> Use a reasonable limit in DFSTestUtil.waitForMetric()
> -
>
> Key: HDFS-9740
> URL: https://issues.apache.org/jira/browse/HDFS-9740
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Kihwal Lee
>Assignee: Chang Li
> Attachments: HDFS-9740.patch
>
>
> If test is detecting a bug, it will probably hit the long surefire timeout
> because the max is {{Integer.MAX_VALUE}}. Use something more realistic. The
> default jmx update interval is 10 seconds, so something like 60 seconds
> should be more than enough.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
