Hello,
We are trying to move our traditional master-slave Solr configuration to
SolrCloud. As our index size is very small (around 1 GB), we are having
only one shard.
So basically, we are having same master-slave configuration with one leader
and 6 replicas.
We are experimenting with maxTime of b
193.0"*
Earlier we were on SOLR 4.4.0 and when we are upgraded to 4.10.0, we
pointed it to the same index we were using for 4.4.0
On Thu, Oct 2, 2014 at 7:11 PM, Shawn Heisey wrote:
> On 10/2/2014 6:58 AM, Sachin Kale wrote:
> > We are trying to move our traditional master-slave So
Apparently, there is a bug in Solr 4.10.0 which was causing the
NullPointerExceptions. SOLR-6501
<https://issues.apache.org/jira/browse/SOLR-6501>
We have updated our production SOLR to 4.10.1
On Thu, Oct 2, 2014 at 8:13 PM, Sachin Kale wrote:
> If I look into the logs, many times I
Is it possible to elect the leader manually in SOLR Cloud 4.10.1?
-Sachin-
- Why you have to keep two nodes on some machines?
- These are very powerful machines (32-Core, 64GB) and our index size
is 1GB. We are allocating 7GB to JVM, so we thought it would be OK to have
two instances on the same machine.
- Physical hardware or virtual machines?
- Physical hardwar
>From ZooKeeper side, we have following configuration:
tickTime=2000
dataDir=/var/lib/zookeeper
clientPort=2181
initLimit=5
syncLimit=2
server.1=192.168.70.27:2888:3888
server.2=192.168.70.64:2889:3889
server.3=192.168.70.26:2889:3889
Also, in solr.xml, we have zkCl
Also, the PingRequestHandler is configured as:
server-enabled.txt
On Fri, Oct 17, 2014 at 9:07 AM, Sachin Kale wrote:
> From ZooKeeper side, we have following configuration:
> tickTime=2000
> dataDir=/var/lib/zookeeper
> clientPort=2181
> initLimit=5
&g
