[
https://issues.apache.org/jira/browse/ACCUMULO-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13608395#comment-13608395
]
Hudson commented on ACCUMULO-1062:
----------------------------------
Integrated in Accumulo-Trunk #790 (See
[https://builds.apache.org/job/Accumulo-Trunk/790/])
ACCUMULO-1062 I suspect large number of threads is making the apache build
servers fail our builds (Revision 1459069)
Result = FAILURE
ecn :
Files :
* /accumulo/trunk
* /accumulo/trunk/assemble
* /accumulo/trunk/core
* /accumulo/trunk/examples
* /accumulo/trunk/fate/src/main/java/org/apache/accumulo/fate/ZooStore.java
*
/accumulo/trunk/fate/src/main/java/org/apache/accumulo/fate/zookeeper/ZooSession.java
* /accumulo/trunk/server
*
/accumulo/trunk/server/src/test/java/org/apache/accumulo/server/tabletserver/InMemoryMapTest.java
* /accumulo/trunk/src
> large numbers of threads make in-memory updates slow
> ----------------------------------------------------
>
> Key: ACCUMULO-1062
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1062
> Project: Accumulo
> Issue Type: Bug
> Components: tserver
> Affects Versions: 1.4.2
> Environment: testing on large clusters
> Reporter: Eric Newton
> Assignee: Eric Newton
> Priority: Critical
> Fix For: 1.5.0, 1.4.3
>
> Attachments: SlamTest.java
>
>
> Using hundreds of ingest programs, each running several batch writers, ingest
> would eventually become slow. Testing (attached) proved that performance
> fell off as the number of threads increased.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
