auto complete search - slow response

2019-07-22 Thread Satya Marivada
Hi All, We have solr 6.3.0 solr cloud running stable. We use an auto complete search functionality where the search is being done after 3 key strokes. Recently we ran into an issue (very slow response from solr) when one of the user hit an auto complete search by typing initial letters of week day

Re: Re: obfuscated password error

2019-03-20 Thread Satya Marivada
e=$SOLR_SSL_CLIENT_TRUST_STORE \ -Djavax.net.ssl.trustStorePassword=$SOLR_SSL_CLIENT_TRUST_STORE_PASSWORD" else SOLR_SSL_OPTS+=" -Djavax.net.ssl.keyStore=$SOLR_SSL_KEY_STORE \ -Djavax.net.ssl.keyStorePassword=$SOLR_SSL_KEY_STORE_PASSWORD \ -Djavax.net.ssl.trustStore=$SOLR_SSL

Re: Re: obfuscated password error

2019-03-20 Thread Satya Marivada
sl.trustStorePassword=$SOLR_SSL_CLIENT_TRUST_STORE_PASSWORD" else SOLR_SSL_OPTS+=" -Djavax.net.ssl.keyStore=$SOLR_SSL_KEY_STORE \ -Djavax.net.ssl.keyStorePassword=$SOLR_SSL_KEY_STORE_PASSWORD \ -Djavax.net.ssl.trustStore=$SOLR_SSL_TRUST_STORE \ -Djavax.net.ssl.trustSto

Re: Re: obfuscated password error

2019-03-19 Thread Satya Marivada
e trust/key stores exist where they are expected, and you can > list the contents with the keytool > - Verify the correct CA certs are trusted > > > Jeremy Branham > jb...@allstate.com > > On 3/18/19, 1:08 PM, "Satya Marivada" wrote: > > Any suggestions ple

Re: Re: obfuscated password error

2019-03-19 Thread Satya Marivada
Verify the correct CA certs are trusted > > > > > > Jeremy Branham > > jb...@allstate.com > > > > On 3/18/19, 1:08 PM, "Satya Marivada" wrote: > > > > Any suggestions please. > > > > Thanks, > > Satya > &

Re: obfuscated password error

2019-03-18 Thread Satya Marivada
Any suggestions please. Thanks, Satya On Mon, Mar 18, 2019 at 11:12 AM Satya Marivada wrote: > Hi All, > > Using solr-6.3.0, to obfuscate the password, have used jetty util to > generate obfuscated password > > > java -cp jetty-uti

obfuscated password error

2019-03-18 Thread Satya Marivada
Hi All, Using solr-6.3.0, to obfuscate the password, have used jetty util to generate obfuscated password java -cp jetty-util-9.3.8.v20160314.jar org.eclipse.jetty.util.security.Password mypassword The output has been used in solr.in.sh as below SOLR_SSL_KEY_STORE=/sanfs/mnt/vol01/solr/solr-

Re: error on health check from command line

2018-07-10 Thread Satya Marivada
Additional information: Using solr-6.3.0 Also tried, no luck: ./bin/solr healthcheck -c poi -z host1:2181,host2:2181,host3:2181 SOLR_AUTH_TYPE=“basic” SOLR_AUTHENTICATION_OPTS="-Dbasicauth=username:password" On Tue, Jul 10, 2018 at 9:09 AM Satya Marivada wrote: > Hi, > >

error on health check from command line

2018-07-10 Thread Satya Marivada
Hi, How do I supply the basic auth credentials for the below healthcheck that has to be done from command line? $ ./bin/solr healthcheck -c poi -z host1:2181,host2:2181,host3:2181 ERROR: Solr requires authentication for https://host1:15101/solr/shard1/. Please supply valid credentials. HTTP code

Re: some solr replicas down

2018-06-20 Thread Satya Marivada
ikely too much pressure on your hardware for some > reason or another. > > Hopefully that helps. > > If anyone with more knowledge about the authentication plugin has > corrections, wants fill in gaps, or has an idea to figure out what requests > cause this issue. It'd be

some solr replicas down

2018-06-18 Thread Satya Marivada
Hi, We are using solr 6.3.0 and a collection has 3 of 4 replicas down and 1 is up and serving. I see a single line error repeating in logs as below. nothing else specific exception apart from it. Wondering what this below message is saying, is it the cause of nodes being down, but saw that this ha

Re: inconsistent results

2018-05-03 Thread Satya Marivada
;re clearing the index first on the > assumption that you're replacing the same docs each time > > One solution people use is to index to a "dark" collection, then use > collection aliasing to atomically switch when the job is done. > > Best, > Erick > > &g

inconsistent results

2018-05-03 Thread Satya Marivada
Hi there, We have a solr (6.3.0) index which is being re-indexed every night, it takes about 6-7 hours for the indexing to complete. During the time of re-indexing, the index becomes flaky and would serve inconsistent count of documents 70,000 at times and 80,000 at times. After the indexing is co

solr index replace with index from another environment

2017-08-28 Thread Satya Marivada
Hi there, We are using solr-6.3.0 and have the need to replace the solr index in production with the solr index from another environment on periodical basis. But the jvms have to be recycled for the updated index to take effect. Is there any way this can be achieved without restarting the jvms? U

Re: indexed vs queried documents count mismatch

2017-08-24 Thread Satya Marivada
ows to compare with Solr? > > On Thu, Aug 24, 2017 at 3:23 PM, Satya Marivada > > wrote: > > > Hi, > > > > I have a weird situation, when I index the documents from admin console > by > > doing "clean, commit and optimize", when the indexing is

indexed vs queried documents count mismatch

2017-08-24 Thread Satya Marivada
Hi, I have a weird situation, when I index the documents from admin console by doing "clean, commit and optimize", when the indexing is completed, it showed 17,920,274 documents are indexed. When queried from the solr admin console from the query tab for all the documents in that collection, it s

cpu utilization high

2017-07-18 Thread Satya Marivada
Hi All, We are using solr-6.3.0 with external zookeeper. Setup is as below. Poi is the collection which is big about 20G with each shard at 10G. Each jvm is having 3G and the vms have 70G of RAM. The processors are at 6. The cpu utilization when running queries is reaching more than 100%. Any sug

Re: node not joining the rest of nodes in cloud

2017-06-16 Thread Satya Marivada
Never mind. I had a different config for zookeeper on second vm which brought a different cloud. On Fri, Jun 16, 2017, 8:48 PM Satya Marivada wrote: > Here is the image: > > https://www.dropbox.com/s/hd97j4d3h3q0oyh/solr%20nodes.png?dl=0 > > There is a node on 002: 15101 port m

Re: node not joining the rest of nodes in cloud

2017-06-16 Thread Satya Marivada
gt; it somewhere else and provide a link. > > Best, > Erick > > > On Fri, Jun 16, 2017 at 3:29 PM, Satya Marivada > > wrote: > > > Hi, > > > > I am running solr-6.3.0. There are4 nodes, when I start solr, only 3 > nodes > > are joining the cl

node not joining the rest of nodes in cloud

2017-06-16 Thread Satya Marivada
Hi, I am running solr-6.3.0. There are4 nodes, when I start solr, only 3 nodes are joining the cloud, the fourth one is coming up separately and not joining the other 3 nodes. Please see below in the picture on admin screen how fourth node is not joining. Any suggestions. Thanks, satya [image:

Re: Out of Memory Errors

2017-06-14 Thread Satya Marivada
Susheel, Please see attached. There heap towards the end of graph has spiked On Wed, Jun 14, 2017 at 11:46 AM Susheel Kumar wrote: > You may have gc logs saved when OOM happened. Can you draw it in GC Viewer > or so and share. > > Thnx > > On Wed, Jun 14, 2017 at 11:26

Out of Memory Errors

2017-06-14 Thread Satya Marivada
Hi, I am getting Out of Memory Errors after a while on solr-6.3.0. The -XX:OnOutOfMemoryError=/sanfs/mnt/vol01/solr/solr-6.3.0/bin/oom_solr.sh just kills the jvm right after. Using Jconsole, I see the nice triangle pattern, where it uses the heap and being reclaimed back. The heap size is set at

Re: file descriptors and threads differing

2017-05-12 Thread Satya Marivada
t; boxes. > > Can't speak to the Java version. > > Best, > Erick > > On Fri, May 12, 2017 at 11:56 AM, Satya Marivada < > satya.chaita...@gmail.com> > wrote: > > > Hi All, > > > > We have a weird problem, with the threads being opened many and

file descriptors and threads differing

2017-05-12 Thread Satya Marivada
Hi All, We have a weird problem, with the threads being opened many and crashing the app in PP7 (one of our environment). It is the same index, same version of solr (6.3.0) and zookeeper (3.4.9) in both environments. Java minor version is different (1.8.0_102 in PP8 (one of our environment) shown

Re: SessionExpiredException

2017-05-11 Thread Satya Marivada
ect > clientPort=2181 > # the maximum number of client connections. > # increase this if you need to handle more clients > #maxClientCnxns=60 > > Thanks, > Satya > > On Mon, May 8, 2017 at 12:04 PM Satya Marivada > wrote: > >> The 3g memory is doing well, performing a

Re: SessionExpiredException

2017-05-11 Thread Satya Marivada
nts #maxClientCnxns=60 Thanks, Satya On Mon, May 8, 2017 at 12:04 PM Satya Marivada wrote: > The 3g memory is doing well, performing a gc at 600-700 MB. > > -XX:+UseConcMarkSweepGC -XX:+UseParNewGC > > Here are my jvm start up > > The start up parameters are: > > java -ser

Re: SessionExpiredException

2017-05-08 Thread Satya Marivada
This is on solr-6.3.0 and external zookeeper 3.4.9 On Wed, May 3, 2017 at 11:39 PM Zheng Lin Edwin Yeo wrote: > Are you using SolrCloud with external ZooKeeper, or Solr's internal > ZooKeeper? > > Also, which version of Solr are you using? > > Regards, > Edwin > &g

OutOfMemoryError and Too many open files

2017-05-08 Thread Satya Marivada
Hi, Started getting below errors/exceptions. I have listed the resolution inline. Could you please see if I am headed right? The below error basically says that there are no more threads can be created as the limit has reached. We have big index and I assume the threads are being created outside

Re: SessionExpiredException

2017-05-08 Thread Satya Marivada
lly, running > > with 6G of memory may lead to _fewer_ noticeable pauses since the > > background threads can do the work, well, in the background. > > > > Best, > > Erick > > > > On Mon, May 8, 2017 at 7:29 AM, Satya Marivada > > wrote: > >> Hi

Re: SessionExpiredException

2017-05-08 Thread Satya Marivada
, 2017 at 12:36 PM Piyush Kunal wrote: > We already faced this issue and found out the issue to be long GC pauses > itself on either client side or server side. > Regards, > Piyush > > On Sat, May 6, 2017 at 6:10 PM, Shawn Heisey wrote: > > > On 5/3/2017 7:32 AM, Satya

solr authentication error

2017-05-04 Thread Satya Marivada
Hi, Can someone please say what I am missing in this case? I have solr 6.3.0, and enabled http authentication, the configuration has been uploaded to zookeeper. But I do see below error in logs sometimes. Are the nodes not able to ciommunicate because of this error? I am not seeing any functional

solr 6.3.0 monitoring

2017-05-03 Thread Satya Marivada
Hi, We stood up solr 6.3.0 with external zookeeper 3.4.9. We are moving to production and setting up monitoring for solr, to check on all cores of a collection to see they are up. Similary any other pointers towards the entire collection monitoring or any other suggestions would be useful. For zo

Re: solr-6.3.0 error port is running already

2017-05-03 Thread Satya Marivada
d in the services file. > > cheers -- Rick > > On 2017-05-02 05:09 PM, Rick Leir wrote: > > Satya > > Say netstat --inet -lP > > You might need to add -ipv4 to that command. The P might be lower case > (I am on the bus!). And the output might show misleading se

SessionExpiredException

2017-05-03 Thread Satya Marivada
Hi, I see below exceptions in my logs sometimes. What could be causing it? org.apache.zookeeper.KeeperException$SessionExpiredException: KeeperErrorCode = Session expired for /overseer at org.apache.zookeeper.KeeperException.create(KeeperException.java:127) at org.apache.zookeeper

Re: solr-6.3.0 error port is running already

2017-05-02 Thread Satya Marivada
at 3:10 PM Satya Marivada wrote: > Hi, > > I am getting the below exception all of a sudden with solr-6.3.0. > "null:org.apache.solr.common.SolrException: A previous ephemeral live node > still exists. Solr cannot continue. Please ensure that no other Solr > process using

solr-6.3.0 error port is running already

2017-05-02 Thread Satya Marivada
Hi, I am getting the below exception all of a sudden with solr-6.3.0. "null:org.apache.solr.common.SolrException: A previous ephemeral live node still exists. Solr cannot continue. Please ensure that no other Solr process using the same port is running already." We are using external zookeeper an

solr directories

2017-03-09 Thread Satya Marivada
Hi, We had solr running on embedded zookeeper. Moved to external zookeeper, as part of this setup on the same vm, had done a fresh solr distribution setup, zookeeper distribution and created new solrdata folder to hold the nodes. All the old folders are archived (zipped and backed up). What wonder

Re: solr warning - filling logs

2017-03-03 Thread Satya Marivada
There is nothing else running on port that I am trying to use: 15101. 15102 works fine. On Fri, Mar 3, 2017 at 2:25 PM Satya Marivada wrote: > Dave and All, > > The below exception is not happening anymore when I change the startup > port to something else apart from that I had

Re: solr warning - filling logs

2017-03-03 Thread Satya Marivada
ou shouldn't use the embedded zookeeper with solr, it's just for > >> development not anywhere near worthy of being out in production. > Otherwise > >> it looks like you may have a port scanner running. In any case don't use > >> the zk that comes with solr

solr warning - filling logs

2017-02-27 Thread Satya Marivada
Hi All, I have configured solr with SSL and enabled http authentication. It is all working fine on the solr admin page, indexing and querying process. One bothering thing is that it is filling up logs every second saying no authority, I have configured host name, port and authentication parameters

Re: solr warning - filling logs

2017-02-26 Thread Satya Marivada
ut in production. Otherwise > it looks like you may have a port scanner running. In any case don't use > the zk that comes with solr > > > On Feb 26, 2017, at 6:52 PM, Satya Marivada > wrote: > > > > Hi All, > > > > I have configured solr with SSL and e

solr warning - filling logs

2017-02-26 Thread Satya Marivada
Hi All, I have configured solr with SSL and enabled http authentication. It is all working fine on the solr admin page, indexing and querying process. One bothering thing is that it is filling up logs every second saying no authority, I have configured host name, port and authentication parameters