[ 
https://issues.apache.org/jira/browse/SOLR-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13627776#comment-13627776
 ] 

matt knecht commented on SOLR-4696:
-----------------------------------

The indexer is a PHP script that's making http calls to the box.  Other than 
the schema, everything else matches dist.  The nodes were never bounced or 
restarted, and I've seen the same behavior on 4.0, 4.1, 4.2 and 4.2.1.  Java 6 
fails much faster on me than any of the java 7's I've tried.  The VMs are bare 
fresh installed ubuntu 12.04.2 base + openssh + tomcat7 and Oracle Java.  
OpenJDK/JRE were removed.

I started out on solr 4.0 with the default 15 second commit and no soft 
commits.  I've gradually lengthened the autocommit time, and also turned off 
calling a commit after X records in the code allowing autocommits to do all 
that work.

I can get a 2 node 2 core 1 shard setup to index all 350k of my documents with 
the same setup.

If there's anything else I can give you to help, I'd be more than happy to 
supply it.  Setup was automated via ansible so its easy to reproduce for me.
                
> All threads become blocked resulting in hang when bulk adding
> -------------------------------------------------------------
>
>                 Key: SOLR-4696
>                 URL: https://issues.apache.org/jira/browse/SOLR-4696
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 4.1, 4.2, 4.2.1
>         Environment: Ubuntu 12.04.2 LTS 3.5.0-27-generic
> Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
> KVM, 4xCPU, 5GB RAM, 4GB heap.
> 4 cores, 2 shards, 2 nodes, tomcat7
>            Reporter: matt knecht
>              Labels: hang
>         Attachments: screenshot-1.jpg, solrconfig.xml, solr.jstack.1, 
> solr.jstack.2
>
>
> During a bulk load after about 150,000 documents load, thread usage spikes, 
> solr no longer processes any documents.  Any additional documents added 
> result in a new thread until the pool is exhausted.

--
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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to