Hi Midas,
According to your autocommit configuration and your worry about commit
time I assume that you are doing explicit commits from client code and
that 1.3s is client observed commit time. If that is the case, than it
might be opening searcher that is taking time.
How do you index data - single threaded or multithreaded? How frequently
do you commit from client? Can you let Solr do soft commits instead of
explicitly committing? Do you have warmup queries? Is this SolrCloud?
What is number of servers (what spec), shards, docs?
In any case monitoring can give you more info about server/Solr behavior
and help you diagnose issues more easily/precisely. One such monitoring
tool is our SPM <http://sematext.com/spm>.
Regards,
Emir
--
Monitoring * Alerting * Anomaly Detection * Centralized Log Management
Solr & Elasticsearch Support * http://sematext.com/
On 10.08.2016 05:20, Midas A wrote:
Thanks for replying
index size:9GB
2000 docs/sec.
Actually earlier it was taking less but suddenly it has increased .
Currently we do not have any monitoring tool.
On Tue, Aug 9, 2016 at 7:00 PM, Emir Arnautovic <
emir.arnauto...@sematext.com> wrote:
Hi Midas,
Can you give us more details on your index: size, number of new docs
between commits. Why do you think 1.3s for commit is to much and why do you
need it to take less? Did you do any system/Solr monitoring?
Emir
On 09.08.2016 14:10, Midas A wrote:
please reply it is urgent.
On Tue, Aug 9, 2016 at 11:17 AM, Midas A <test.mi...@gmail.com> wrote:
Hi ,
commit is taking more than 1300 ms . what should i check on server.
below is my configuration .
<autoCommit> <maxTime>${solr.autoCommit.maxTime:15000}</maxTime> <
openSearcher>false</openSearcher> </autoCommit> <autoSoftCommit>
<maxTime>
${solr.autoSoftCommit.maxTime:-1}</maxTime> </autoSoftCommit>
--
Monitoring * Alerting * Anomaly Detection * Centralized Log Management
Solr & Elasticsearch Support * http://sematext.com/
