On client side timeout is set to 5s but when I look in solr log I see QTime
less than 5000 (in ms). We use jetty to start solr process, where should I look
for directives connected with timeouts?
st regards,
Rafał Radecki.
Hi All.
I have some solr 3.5.0 instances on CentOS 6 x86_64. Currently logging is
by going to syslog (logger), for all my cores to one shared logfile. I
would like to have a separate logfile for each core.
My solr process is started from a simple shell script:
daemon $JAVA -Xms25g -Xmx25g -DSTOP
Yes, this is solr 4.1.
2013/3/20 Mark Miller :
> Hmm, I'd have to look, but first to make, this subject says 4.1?
>
> In 4.1 the slave will be ahead because it commits after installing the index.
> In 4.2 it shouldn't.
>
> Your on?
>
> - Mark
>
> On Mar 20
sponse format is experimental. It is likely to change in the future.
Which line with "indexVersion" should I use?
Best regards,
Rafal Radecki.
2013/3/19 Mark Miller :
>
> On Mar 15, 2013, at 6:43 AM, Rafał Radecki wrote:
>
>> I use http and get /solr/replication?com
I use http and get /solr/replication?command=indexversion urls to get
index versions on master and slave. The replication works fine but
index versions from /solr/replication?command=indexversion differ.
Best regards,
Rafal.
2013/3/14 Mark Miller :
> What calls are you using to get the versions?
CET 2013
5
23214
0
Thu Mar 14 13:15:53 CET 2013
true
false
This response format is experimental. It is likely to change in the future.
Which one should be used? Is there any other way to monitor idex
version on master and slave?
Best regards,
Rafał Radecki.
2013/3/14 Rafał Radecki :
>
Hi All.
I am monitoring two solr 4.1 solr instances in master-slave setup. On
both nodes I check url /solr/replication?command=details and parse it
to get:
- on master: if replication is enabled -> field replicationEnabled
- on slave: if replication is enabled -> field replicationEnabled
- on slav
