5.x will still build a war file that you an deploy on Tomcat. But
support for that is going away eventually, certainly by 6.0. But you
do have to make the decision sometime before 6.0 at least.
Best,
Erick
On Wed, May 27, 2015 at 1:24 PM, Vishal Swaroop vishal@gmail.com wrote:
Thanks a lot
Currently, we have SOLR configured on single linux server (24 GB physical
memory) with multiple cores.
We are using SOLR joins (https://wiki.apache.org/solr/Join) across cores on
this single server.
But, as data will grow to ~2 billion we need to assess whether we’ll need
to run SolrCloud as In a
Hard to say. I've seen 20M doc be the place you need to consider
sharding/SolrCloud. I've seen 300M docs be the place you need to start
sharding. That said I'm quite sure you'll need to shard before you get
to 2B. There's no good reason to delay that process.
You'll have to do something about the
Thanks a lot Erick... You are right we should not delay moving to
sharding/SolrCloud process.
As you all are expert... currently we are using SOLR 4.7.. Do you suggest
we should move to latest SOLR release 5.1.0 ? or we can manage the above
issue using SOLR 4.7
Regards
Vishal
On Wed, May 27,
I'd move to Solr 4.10.3 at least, but preferably Solr 5.x. Solr 5.2 is
being readied for release as we speak, it'll probably be available in
a week or so barring unforeseen problems and that's the one I'd go
with by preference.
Do be aware, though, that the 5.x Solr world deprecates using a war
