Possible bug in cluster status - > solr 8.3

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Possible bug in cluster status - > solr 8.3

Jacek Kikiewicz
I found interesting situation, I've created a collection with only one replica.
Then I scaled solr-cloud cluster, and run  'addreplica' call to add 2 more.
So I have a collection with 3 tlog replicas, cluster status page shows
them but shows also this:
              "core_node2":{
                "core":"EDITED_NAME_shard1_replica_t1",
                "base_url":"http://EDITED_NODE:8983/solr",
                "node_name":"EDITED_NODE:8983_solr",
                "state":"active",
                "type":"TLOG",
                "force_set_state":"false",
                "leader":"true"},
              "core_node5":{
                "core":"EDITED_NAME_shard1_replica_t3",
                "base_url":"http://EDITED_NODE:8983/solr",
                "node_name":"EDITED_NODE:8983_solr",
                "state":"active",
                "type":"TLOG",
                "force_set_state":"false"},
              "core_node6":{
                "core":"EDITED_NAME_shard1_replica_t4",
                "base_url":"http://EDITED_NODE:8983/solr",
                "node_name":"EDITED_NODE:8983_solr",
                "state":"active",
                "type":"TLOG",
                "force_set_state":"false"}}}},
        "router":{"name":"compositeId"},
        "maxShardsPerNode":"1",
        "autoAddReplicas":"false",
        "nrtReplicas":"1",
        "tlogReplicas":"1",
        "znodeVersion":11,


As you can see I have 3 replicas but then I have also: "tlogReplicas":"1"

If I create collection with tlogReplicas=3 then cluster status shows
"tlogReplicas":"3"
IS that a bug or somehow 'works as it should' ?

Regards,
Jacek
Reply | Threaded
Open this post in threaded view
|

Re: Possible bug in cluster status - > solr 8.3

Jason Gerlowski
It seems like an issue to me.  Can you open a JIRA with these details?

On Fri, Nov 15, 2019 at 10:51 AM Jacek Kikiewicz <[hidden email]> wrote:

>
> I found interesting situation, I've created a collection with only one replica.
> Then I scaled solr-cloud cluster, and run  'addreplica' call to add 2 more.
> So I have a collection with 3 tlog replicas, cluster status page shows
> them but shows also this:
>               "core_node2":{
>                 "core":"EDITED_NAME_shard1_replica_t1",
>                 "base_url":"http://EDITED_NODE:8983/solr",
>                 "node_name":"EDITED_NODE:8983_solr",
>                 "state":"active",
>                 "type":"TLOG",
>                 "force_set_state":"false",
>                 "leader":"true"},
>               "core_node5":{
>                 "core":"EDITED_NAME_shard1_replica_t3",
>                 "base_url":"http://EDITED_NODE:8983/solr",
>                 "node_name":"EDITED_NODE:8983_solr",
>                 "state":"active",
>                 "type":"TLOG",
>                 "force_set_state":"false"},
>               "core_node6":{
>                 "core":"EDITED_NAME_shard1_replica_t4",
>                 "base_url":"http://EDITED_NODE:8983/solr",
>                 "node_name":"EDITED_NODE:8983_solr",
>                 "state":"active",
>                 "type":"TLOG",
>                 "force_set_state":"false"}}}},
>         "router":{"name":"compositeId"},
>         "maxShardsPerNode":"1",
>         "autoAddReplicas":"false",
>         "nrtReplicas":"1",
>         "tlogReplicas":"1",
>         "znodeVersion":11,
>
>
> As you can see I have 3 replicas but then I have also: "tlogReplicas":"1"
>
> If I create collection with tlogReplicas=3 then cluster status shows
> "tlogReplicas":"3"
> IS that a bug or somehow 'works as it should' ?
>
> Regards,
> Jacek
Reply | Threaded
Open this post in threaded view
|

Re: Possible bug in cluster status - > solr 8.3

Andrzej Białecki-2
AFAIK these collection properties are not tracked that faithfully and can get out of sync, mostly because they are used only during collection CREATE and BACKUP / RESTORE and not during other collection operations or during searching / indexing. SPLITSHARD doesn’t trust them, instead it checks the actual counts of existing replicas.

These out-of-sync counts may actually cause problems in BACKUP / RESTORE, which is worth checking.

There are also conceptual issues here, eg. “replicationFactor” becomes meaningless as soon as we have different counts of NRT / TLOG / PULL replicas.

> On 21 Nov 2019, at 13:40, Jason Gerlowski <[hidden email]> wrote:
>
> It seems like an issue to me.  Can you open a JIRA with these details?
>
> On Fri, Nov 15, 2019 at 10:51 AM Jacek Kikiewicz <[hidden email]> wrote:
>>
>> I found interesting situation, I've created a collection with only one replica.
>> Then I scaled solr-cloud cluster, and run  'addreplica' call to add 2 more.
>> So I have a collection with 3 tlog replicas, cluster status page shows
>> them but shows also this:
>>              "core_node2":{
>>                "core":"EDITED_NAME_shard1_replica_t1",
>>                "base_url":"http://EDITED_NODE:8983/solr",
>>                "node_name":"EDITED_NODE:8983_solr",
>>                "state":"active",
>>                "type":"TLOG",
>>                "force_set_state":"false",
>>                "leader":"true"},
>>              "core_node5":{
>>                "core":"EDITED_NAME_shard1_replica_t3",
>>                "base_url":"http://EDITED_NODE:8983/solr",
>>                "node_name":"EDITED_NODE:8983_solr",
>>                "state":"active",
>>                "type":"TLOG",
>>                "force_set_state":"false"},
>>              "core_node6":{
>>                "core":"EDITED_NAME_shard1_replica_t4",
>>                "base_url":"http://EDITED_NODE:8983/solr",
>>                "node_name":"EDITED_NODE:8983_solr",
>>                "state":"active",
>>                "type":"TLOG",
>>                "force_set_state":"false"}}}},
>>        "router":{"name":"compositeId"},
>>        "maxShardsPerNode":"1",
>>        "autoAddReplicas":"false",
>>        "nrtReplicas":"1",
>>        "tlogReplicas":"1",
>>        "znodeVersion":11,
>>
>>
>> As you can see I have 3 replicas but then I have also: "tlogReplicas":"1"
>>
>> If I create collection with tlogReplicas=3 then cluster status shows
>> "tlogReplicas":"3"
>> IS that a bug or somehow 'works as it should' ?
>>
>> Regards,
>> Jacek
>