Yes, we are sure that this is not typo.
Actually we did more experiments and found that
1) https://hostname:8983/solr/my_collection/select?ids=169455599|1
2) https://hostname:8983/solr/my_collection/select?q=id:169455599|1
3) https://hostname:8983/solr/my_collection/get?ids=169455599|1
1) thro
We are using SolrCloud 7.7.2 and having some trouble with multi shards.
The initial number of shards in the collection was one(and 3 replica), and
we have recently split a shard into 4 shards(and 3 replica for each shard)
by using API call :
/admin/collections?action=SPLITSHARD&collection=name&sha
tivity, the upgrade path 6>7>8 is quiet natural. From my
point of view, we must speak about “since Lucene 6, version is compatible
previous major version of an index” not upgrading. The term is ambiguous.
The thinks must be clear, I understand the problem :-)
Jean louis
> Le 19 mai 2020
D&reserved=0
(my blog)
> On May 19, 2020, at 6:21 AM, VILA Jean-Louis
> wrote:
>
> Many thanks for your answers Erik.
>
> Effectively, I've read this into many different threads that the migration
> path will not be guaranteed but, what's strange is that t
version which v6! So forbid to open v7 lucene indexes upgraded
from v6, is quiet brutal and the rule about that we can migrate only from
previous major version is not completely true :-(
I'll stay into v7.7.3
Thanks again,
Jean-Louis
-Original Message-
From: Erick Eric
est: open reader.OK [took 2.779 sec]
When I read the different thread, some people say that when a segment is
"marked as v6 lucene index", this mark remains across upgrading, so we are
stucked in 7.7.3 version.
What are my options?
Many many thanks for your help,
Jean-Louis
tlogTotalSize is
zero).
I guess Solr stores tlogs count in its memory and tries to recover tlogs
files when it reloads collections, which brings back a bunch of tlogs with
zero size.
Is there any way(hopefully rest api) to delete tlogs from disk as well as
memory in Solr?
Thanks.
Louis
tlogTotalSize is
zero).
I guess Solr stores tlogs count in its memory and tries to recover tlogs
files.
Is there any way(hopefully rest api) to delete tlogs from disk as well as
memory in Solr?
Thanks.
Louis
--
Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Another finding is, no matter how I tried to disable buffer with the
following setup on target node, it is always enabled first time.
disabled
Once I call CDCR API to disable buffer, it turns to be disabled. I wonder if
https://issues.apache.org/jira/browse/SOLR-11652 is related to
Using Solr 7.7.3-snapshot, 1 shard + 3 replicas on source and target cluster
When unidirectional CDCR enabled and buffer disabled, my understanding is,
when data is successfully forwarded to target and committed, tlogs on both
source and target should be purged.
However, the source node doesn't p
* Environment: Solr Cloud 7.7.0, 3 nodes / CDCR bidirectional / CDCR buffer
disabled
Hello All,
I have some problem with tlog. They are getting bigger and bigger...
They don't seem to be deleted at all even after hard commit, so now the
total size of tlog files is more than 21GB..
Actually I se
I just saw this article.
https://issues.apache.org/jira/browse/SOLR-13349
Can my issue be related to this?
--
Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
* Solr Version 7.7. Using Cloud with CDCR
* 3 replicas 1 shard on production and disaster recovery
Hi,
Last week, I posted a question about tlogs -
https://lucene.472066.n3.nabble.com/tlogs-are-not-deleted-td4451323.html#a4451430
I disabled buffer based on the advice, but still, tlogs in "produc
* Solr Version 7.7. Using Cloud with CDCR
* 3 replicas 1 shard on production and disaster recovery
Hi,
Last week, I posted a question about tlogs -
https://lucene.472066.n3.nabble.com/tlogs-are-not-deleted-td4451323.html#a4451430
I disabled buffer based on the advice, but still, tlogs in "produc
Thank you for advice.
I will disable it and check if tlogs will disappear.
--
Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html
15 matches
Mail list logo
