I am sorry about a type mistake 8,000,000,000 -> 800,000,000
2013/5/27 Jam Luo
> I have the same problem. at 4.1 ,a solr instance could take 8,000,000,000
> doc. but at 4.2.1, a instance only take 400,000,000 doc, it will oom at
> facet query. the facet field was token by space
I have the same problem. at 4.1 ,a solr instance could take 8,000,000,000
doc. but at 4.2.1, a instance only take 400,000,000 doc, it will oom at
facet query. the facet field was token by space.
May 27, 2013 11:12:55 AM org.apache.solr.common.SolrException log
SEVERE: null:java.lang.RuntimeExcep
I build indexes by EmbeddedSolrServer, then move them to the online
system. The online system do not add new Documents. So the hashcode range
is not important, I need add shard only. how do I customise it?
thanks
2013/3/10 adfel70
> Mark, what's the current estimation for official 4.2 release
OK, I will try to upgrade Oracle java and the lastest solr. thanks
2012/12/19 Shawn Heisey
> On 12/18/2012 8:18 PM, Jam Luo wrote:
> > I deployed a solr-4.0-beta cluster, 4 shard, 2 peers in a shard. A peer
> > catch exception:
> > 十二月 18, 2012 7:56:31 下午 org.apache.solr
Yes, I have the same problem.
2012/10/5 Kyryl Bilokurov
> Hi,
>
> I have a functional/performance test SolrCloud cluster (using Solr
> 4.0-BETA) with the following setup: 4 servers, each server hosts 1/4th of
> the collection (no replicas, so there are only leaders for each shard).
> Current ZK
space?
>
> > if I stop query more then ten minutes, the solr instance will start
> normally.
>
> Maybe queries are piling up in threads before the server is ready to
> handle them and then trying to handle them all at once gives an OOM?
> Is this live t
hould not be necessary, yonik
> just committed a fix for that a bit ago.
>
> On Aug 7, 2012, at 9:41 AM, Mark Miller wrote:
>
> >
> > On Aug 7, 2012, at 5:49 AM, Jam Luo wrote:
> >
> >> Hi
> >> I have big index data files more then 200g, there a
Hi
I deployed a solr cluster,the code version is
"NightlyBuilds apache-solr-4.0-2012-03-19_09-25-37".
Cluster has 4 nodes named "A", "B", "C", "D", "num_shards=2", A and
C in shard1 , B and D in shard2, A and B is the leader of their shard. It
has ran 2 days, added 20m docs, all of th
