Re: Error creating collection

2014-06-23 Thread pravin
Thanks Eric for your suggestion. It helped me by increasing the znode data size from 1M to 2M. Here is the reference for the same to change this configuration: https://zookeeper.apache.org/doc/r3.3.2/zookeeperAdmin.html I used this parameter in the JAVA_OPTS -Djute.maxbuffer=2M which helped me to

Re: Error creating collection

2014-06-23 Thread Erick Erickson
I suspect (but don't know for sure) that the problem here is that ZK is limited to 1M at the moment, although this is configurable (sorry, don't have the reference handy). But at 3,000 cores you're certainly going into relatively uncharted territory so I'm unsurprised that you're running into edge

Re: Error creating collection

2014-06-23 Thread pravin
I am also facing this issue recently. Any solution to fix this issue? I have almost 3000+ core created and adding some more. Please suggest if there is restriction on the core numbers and shard and collection. Here is trace: Jun 23, 2014 9:01:45 AM org.apache.solr.common.SolrException log SEVERE

Re: Error creating collection

2013-04-23 Thread yriveiro
The solr version is 4.2.1. Here the stack trace: SEVERE: org.apache.solr.common.SolrException: Error CREATEing SolrCore XXX': Could not get shard_id for core: XXX coreNodeName:192.168.20.47:8983_solr_XXX$ at org.apache.solr.handler.admin.CoreAdminHandler.handleCreateAction(CoreAdminHandler.java:4

Re: Error creating collection

2013-04-22 Thread Erick Erickson
What version of Sor? More context for the stack trace? You might want to review: http://wiki.apache.org/solr/UsingMailingLists Best Erick On Mon, Apr 22, 2013 at 5:33 AM, yriveiro wrote: > I get this exception when I try to create a new collection. someone have any > idea that what's going on?

Re: Error creating collection using CORE-API

2013-03-26 Thread Joel Bernstein
What version of Solr are you using? I'll see if I can reproduce the problem. Your initial error, which I believe was because Solr could not find the matching config-set in zookeeper, I've run into many times. But I've never had a problem when I've re-issued the command with a matching config-set.