Topic LIVE-REPLICAS shows spu id 0 (but there is no such SPU installed)

[ajhunyady]

$ ./target/debug/fluvio topic create test -p 1 -r 2
topic "test" created


$  ./target/debug/fluvio topic describe -t test
 Name                    :  test 
 Type                    :  computed 
 Partition Count         :  1 
 Replication Factor      :  2 
 Ignore Rack Assignment  :  - 
 Status                  :  provisioned 
 Reason                  :  - 
 Partition Map               
 -----------------           
     ID      LEADER      REPLICAS          LIVE-REPLICAS 
      0       5003       [5003, 5001]      [0, 5001] 


$  ./target/debug/fluvio spu list
 ID    NAME             STATUS  TYPE    RACK  PUBLIC          PRIVATE 
 5001  custom-spu-5001  online  custom   -    localhost:9010  localhost:9011 
 5002  custom-spu-5002  online  custom   -    localhost:9020  localhost:9021 
 5003  custom-spu-5003  online  custom   -    localhost:9030  localhost:9031 

[sehz]

In the kubernetes,

kc get partitions
NAME     LEADER   FOLLOWERS     STATUS   LSR   HW    EOF   FOLLOWER OFFSETS
test-0   5002     [5002 5001]   Online   2     0     0     [map[hw:0 leo:0 spu:0] map[hw:0 leo:0 spu:5001]]

so looks like wrong id is populated

[ajhunyady]

I guess so, of 5002 is a leader and a follower at the same time?

[sehz]

Not sure. Will confirm thru more debugging

[sehz]

We need to ensure LSR is properly calculated. Assigning to Nick.
LSR (Live Replica) is number of replica (including leader) that has caught up with leader

in this following scenario, LSR should be 2 (including leader):

flvd partition list
 TOPIC    PARTITION  LEADER  REPLICAS  RESOLUTION  HW  LEO  LSR  FOLLOWER OFFSETS 
 message  0          5001    [5002]    Online      0   0    1    [ReplicaStatus { spu: 5002, hw: 0, leo: 0 }] 

This is same as Kafka's in-sync-replica: https://docs.cloudera.com/runtime/7.2.0/kafka-overview/topics/kafka-overview-leader-positions-replicas.html

[github-actions]

Stale issue message

[sehz]

this should be fixed