It's been a while since I had time to look further into this. I'll have to
go back through logs, which I need to get retrieved by an admin.
On Fri, Mar 23, 2018 at 8:45 AM, Amrit Sarkar
wrote:
> Elaino,
>
> When you say commits not working, the solr logs not printing "commit"
> messages? or docu
Elaino,
When you say commits not working, the solr logs not printing "commit"
messages? or documents are not appearing when we search.
Amrit Sarkar
Search Engineer
Lucidworks, Inc.
415-589-9269
www.lucidworks.com
Twitter http://twitter.com/lucidworks
LinkedIn: https://www.linkedin.com/in/sarkaram
I'm just catching up on reading solr emails, so forgive me for being late
to this dance
I've just gone through a project to enable CDCR on our Solr, and I also
experienced a small period of time where the commits on the source server
just seemed to stop. This was during a period of intense ex
I meant to get back to this sooner.
When I say I issued a commit I do issue it as collection/update?commit=true
The soft commit interval is set to 3000, but I don't have a problem with
soft commits ( I think). I was responding
I am concerned that some hard commits don't seem to happen, but I thi
bq: But if 3 seconds is aggressive what would be a good value for soft commit?
The usual answer is "as long as you can stand". All top-level caches are
invalidated, autowarming is done etc. on each soft commit. That can be a lot of
work and if your users are comfortable with docs not showing up f
Erick, I am aware of the CDCR buffering problem causing tlog retention, we
always turn buffering off in our cdcr configurations.
My post was precipitated by seeing that we had uncommitted data in
collections > 24 hours after it was loaded. The collections I was looking
at are in our development en
On 2/9/2018 9:29 AM, Webster Homer wrote:
A little more background. Our production Solrclouds are populated via CDCR,
CDCR does not replicate commits, Commits to the target clouds happen via
autoCommit settings
We see relvancy scores get inconsistent when there are too many deletes
which seems t
Do you by any chance have buffering turned on for CDCR? That parameter
is misleading. If true, tlogs will accumulate forever. The blanket
recommendation is becoming turn buffering off and leave it off, the
original intention there has been replaced really by bootstrapping.
Buffering was there for m
A little more background. Our production Solrclouds are populated via CDCR,
CDCR does not replicate commits, Commits to the target clouds happen via
autoCommit settings
We see relvancy scores get inconsistent when there are too many deletes
which seems to happen when hard commits don't happen.
On
I we do have autoSoftcommit set to 3 seconds. It is NOT the visibility of
the records that is my primary concern. I am concerned about is the
accumulation of uncommitted tlog files and the larger number of deleted
documents.
I am VERY familiar with the Solr documentation on this.
On Fri, Feb 9, 2
On 2/9/2018 8:44 AM, Webster Homer wrote:
I look at the latest timestamp on a record in the collection and see that
it is over 24 hours old.
I send a commit to the collection, and then see that the core is now
current, and the segments are fewer. The commit worked
This is the setting in solrcon
11 matches
Mail list logo