[
https://issues.apache.org/jira/browse/HADOOP-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526322
]
Hadoop QA commented on HADOOP-1870:
-----------------------------------
-1, build or testing failed
2 attempts failed to build and test the latest attachment
http://issues.apache.org/jira/secure/attachment/12365507/patch.txt against
trunk revision r574389.
Test results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/727/testReport/
Console output:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/727/console
Please note that this message is automatically generated and may represent a
problem with the automation system and not the patch.
> [hbase] Parameters for TestDFSAbort too aggressive
> --------------------------------------------------
>
> Key: HADOOP-1870
> URL: https://issues.apache.org/jira/browse/HADOOP-1870
> Project: Hadoop
> Issue Type: Bug
> Components: contrib/hbase
> Affects Versions: 0.15.0
> Reporter: Jim Kellerman
> Assignee: Jim Kellerman
> Fix For: 0.15.0
>
> Attachments: patch.txt
>
>
> The parameter settings for client retries both at the Hadoop IPC level and at
> the HBase client level seem to aggressive. Even though
> lucene.zones.apache.org is a quad CPU machine, it routinely displays a load
> average of ~8. It runs much slower than any of our test machines: Core 2 duo
> MacBook Pro (running Linux or MacOs), Dual dual-core opterons (Linux), Core
> 2 (Windows) and even a PentiumM (Windows).
> Consequently, tests that run just fine in the environments listed above
> sometimes fail on lucene.zones.
> It is unclear if this is due to thread scheduling differences between Solaris
> and Linux/Windows or in the respective JVM's.
> To make some tests run reliably in the Hudson build environment, we sometimes
> have to increase retries and timeouts, which we set aggressively so that the
> tests will run faster.
> If that is what it takes to prevent Hudson build failures, then so be it. The
> tests may take longer to run, but if that is the tradeoff to achieve
> reliability, then so be it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
