Re: Shard replica labels in Solr Admin graph?

On 2/28/2018 5:42 PM, Scott Prentice wrote: We initially tested our Solr Cloud implementation on a single VM with 3 Solr servers and 3 Zookeeper servers. Once that seemed good, we moved to 3 VMs with 1 Solr/Zookeeper on each. That's all looking good, but in the Solr Admin > Cloud > Graph, all

Re: Configuration of SOLR Cluster

On 2/28/2018 6:54 AM, James Keeney wrote: I did notice one thing in the logs: 2018-02-28 13:21:58,932 [myid:1] - INFO [/172.31.86.130:3888:QuorumCnxManager$Listener@743] - *Received connection request /172.31.73.122:34804 * When the restarted node attempts to

Shard replica labels in Solr Admin graph?

We initially tested our Solr Cloud implementation on a single VM with 3 Solr servers and 3 Zookeeper servers. Once that seemed good, we moved to 3 VMs with 1 Solr/Zookeeper on each. That's all looking good, but in the Solr Admin > Cloud > Graph, all of my shard replicas are on "127.0.1.1" ..

RE: Gentle reminder RE: Object not fetched because its identifier appears to be already in processing

Information Classification: ll Limited Access Thank you for your reply Shawn. I'm not part of that user list so I never received any emails so far. Could you please subscribe me (vyeleswar...@statestreet.com) or let me know the process? Also I would greatly appreciate if you could forward any

Re: When the number of collections exceeds one thousand, the construction of indexing speed drops sharply

On 2/28/2018 2:53 AM, 苗海泉 wrote: Thanks for your detailed advice, the monitor product you are talking about is good, but our solr system is running on a private network and seems to be unusable at all, with no single downloadable application for analyzing specific gc logs. For analyzing GC

Re: Defining Document Transformers in Solr Configuration

I am not sure I fully understood the desired transformation, but perhaps something from https://people.apache.org/~hossman/rev2016/ would help. I am specifically thinking of: *) f.person.qf example *) ${people} example Regards, Alex. On 27 February 2018 at 15:20, simon

Re: Defining Document Transformers in Solr Configuration

Thanks Mikhail: I considered that, but not all queries would request that field, and there are in fact a couple more similar DocTransformer-generated aliased fields which we can optionally request, so it's not a general enough solution. -Simon On Wed, Feb 28, 2018 at 1:18 AM, Mikhail Khludnev

Re: When the number of collections exceeds one thousand, the construction of indexing speed drops sharply

If you are after only visualising GC, there are several tools that you can download or upload logs to visualise. If you would like to monitor all host/solr/jvm, Sematext’s SPM also comes in on-premises version, where you install and host your own monitoring infrastructure:

Re: When the number of collections exceeds one thousand, the construction of indexing speed drops sharply

Thanks for your detailed advice, the monitor product you are talking about is good, but our solr system is running on a private network and seems to be unusable at all, with no single downloadable application for analyzing specific gc logs. 2018-02-28 16:57 GMT+08:00 Emir Arnautović

Authentication and distributed search in 7.2.1

Hi, In 7.2.1 there's the authentication module and associated security.json file, which works well for single cores. (Note: standalone mode, no SolrCloud) It doesn't appear to work with distributed searches, including multi-shard local searches . e.g.

RE: Gentle reminder RE: Object not fetched because its identifier appears to be already in processing

Information Classification: ll Limited Access Thanks Shawn, I submitted a request to subscribe. After restarting jboss and redeploying solr war files, index files were successfully created and global search is now working. Not sure what really was the problem and what was fixed. :) We spent few

Re: When the number of collections exceeds one thousand, the construction of indexing speed drops sharply

Hi, I would start with following: 1. have dedicated nodes for ZK ensemble - those do not have to be powerful nodes (maybe 2-4 cores and 8GB RAM) 2. reduce heap size to value below margin where JVM can use compressed oops - 31GB should be safe size 3. shard collection to all nodes 4. increase