On 7/20/2020 10:30 AM, yaswanth kumar wrote:
1# I did make sure that zoo.cfg got the proper data dir and its not
pointing to temp folder; do I need to set the variables in ZK_ENV.sh. as
well on top of the zoo.cfg ??
Those are questions about the ZK server, which we are not completely
On 7/19/2020 1:37 AM, yo tomi wrote:
I have no choice but use post-processor.
However bug of SOLR-8030 makes me not feel like using it.
Can you explain why you need the trim field and remove blank field
processors to be post processors? When I think about these
functionalities, they should
I installed SOLR 8.x but then realized I needed 7.7.x for my purposes. I
uninstall 8.x and installed 7.7.3 no problem.
However, it seems to have issue with port 8983. This is what I get when I
try to open the UI in a browser, which I assume is due to some not
uninstall 8.x artifact:
HTTP ERROR
Hi,
It's very hard to answer questions like 'how fast/slow might this be' -
the best way to find out is to try, e.g. to build a prototype that you
can time. To be useful this prototype should use representative data and
queries. Once you have this, you can try improving performance with
Hi Austin,
Sitecore is a commercial product so your first port of call should be
whoever sold you or is supporting Sitecorea quick (and by no means
deep) bit of research shows this error may be generated by the Sitecore
indexer process calling Solr. We won't be able to see how it does
I am using Solr version 6.1.0, Java 8 version and G1GC on production. We have 2
shards and each shard has 1 replica.
Some times my replica goes into recovery mode and when I check my GC log, I can
not find the GC pause time more than 600 milliseconds. sometimes GC pause time
goes near to 1
FWIW the real error is msg":"SolrCore is loading which is bad if you are in the
middle of indexing
What is happening on solr at this time?
> On Jul 20, 2020, at 4:46 AM, Charlie Hull wrote:
>
> Hi Austin,
>
> Sitecore is a commercial product so your first port of call should be whoever
>
Hi,
After upgrading from Solr 6.6.2 to 7.6.0, we're seeing an issue with
request routing in CloudSolrClient. It seems that we've lost the ability to
route a request to a specific core of a node.
For example, if a host is serving shard 1 core 1, and shard 2 core
1, @6.6.2, adding a "_route_="
First I want to check if this is an XY problem. Why do you want to do this?
If you’re using CloudSolrClient, requests are automatically load balanced. And
even if you send a top-level request (assuming you do NOT set distrib=false),
then the request may be forwarded to another Solr node anyway.
Our use case here is that we want to highlight a single document (against
user-provided keywords), and we know the document's unique key already.
So this is really not a distributed query, but more of a get by id, but we
use SolrClient.query() for highlighting capabilities.
And since we know the
Hmm, ok.
I’d have to defer to David Smiley about whether that was an intended change.
I’m curious whether you can actually measure the difference in performance. If
you can then that changes the urgency. Of course it’ll be a little more
expensive
for the replica serving shard2 on that machine
This error seems similar to what we are having:
http://mail-archives.apache.org/mod_mbox/lucene-dev/201907.mbox/%3ccapswd+oa5n3f2xqj0o58dqokpwudaefhynagoqg7rg3y8cu...@mail.gmail.com%3E
Austin Kimmel
Software Developer
Vail Resorts, Inc.
303-404-1922
akim...@vailresorts.com
VAILRESORTS®
Some possibilities:
1> you haven’t changed your data dir for Zookeeper from the default
"/tmp/zookeeper”
2> you aren’t pointing to the Zookeepers you think you are. In particular are
you running embedded zookeeper? This should be apparent if you look on the
admin page ant the zookeeper URLs
Thanks Erick for a quick response.
Here are my responses for your questions
1# I did make sure that zoo.cfg got the proper data dir and its not
pointing to temp folder; do I need to set the variables in ZK_ENV.sh. as
well on top of the zoo.cfg ??
2# I can confirm that we are not using the
HI Team,
Can someone help me understand on what could be the reason to lose both
zookeeper data and also the collection information that will be stored for
each collection in the path ../solr/server/solr/
Here are the details of what versions that we use
Solr - 8.2
Zookeeper 3.4.14
Two node
Hello,
I've been in contact with Sitecore Support, but they say that the issue is on
the Solr side. I see the errors when I am trying to rebuild the indexes. The
index is populated the first time and then each sequential time that I try to
rebuild the index it or access it there is an error.
So how do we recover from such state ? When I am trying addreplica , it
returns me 503. Also my node has multiple replicas out of them most are
dead. How do we make get rid of those dead replicas via script. ?is that a
possibility?
On Mon, 20 Jul 2020 at 11:00 AM, Radu Gheorghe
wrote:
> Hi
17 matches
Mail list logo
