[Bug] Bookie handle is not available for a long time.

[mattisonchao]

Search before asking

• I searched in the issues and found nothing similar.

Version

Broker: 2.10+

• Bk Client uses PulsarRegistrationClient
• Bookie uses ZKRegistrationManager

Description

The problem occurs when the bookie state changes from read-only to writable or vice versa.

"Jun 16, 2023 @ 16:33:35.960","2023-06-16T16:33:35,959+0000 [main-EventThread] INFO  org.apache.pulsar.metadata.bookkeeper.PulsarRegistrationClient - Update BookieInfoCache (readonly bookie) main-bk-2:3181 -> BookieServiceInfo{properties={}, endpoints=[EndpointInfo{id=httpserver, port=8000, host=0.0.0.0, protocol=http, auth=[], extensions=[]}, EndpointInfo{id=bookie, port=3181, host=main-bk-2, protocol=bookie-rpc, auth=[], extensions=[]}]}","main-broker-1"
"Jun 16, 2023 @ 16:33:35.959","2023-06-16T16:33:35,959+0000 [main-EventThread] INFO  org.apache.pulsar.metadata.bookkeeper.PulsarRegistrationClient - Update BookieInfoCache (readonly bookie) main-bk-2:3181 -> BookieServiceInfo{properties={}, endpoints=[EndpointInfo{id=httpserver, port=8000, host=0.0.0.0, protocol=http, auth=[], extensions=[]}, EndpointInfo{id=bookie, port=3181, host=main-bk-2, protocol=bookie-rpc, auth=[], extensions=[]}]}","main-broker-1"
"Jun 16, 2023 @ 16:33:35.918","2023-06-16T16:33:35,918+0000 [main-EventThread] INFO  org.apache.pulsar.metadata.bookkeeper.PulsarRegistrationClient - Update BookieInfoCache (readonly bookie) main-bk-2:3181 -> BookieServiceInfo{properties={}, endpoints=[EndpointInfo{id=httpserver, port=8000, host=0.0.0.0, protocol=http, auth=[], extensions=[]}, EndpointInfo{id=bookie, port=3181, host=main-bk-2, protocol=bookie-rpc, auth=[], extensions=[]}]}","main-broker-0"
"Jun 16, 2023 @ 16:33:35.909","2023-06-16T16:33:35,909+0000 [metadata-store-10-1] INFO  org.apache.pulsar.metadata.bookkeeper.PulsarRegistrationClient - Bookie main-bk-2:3181 disappeared","main-broker-1"
"Jun 16, 2023 @ 16:33:35.909","2023-06-16T16:33:35,909+0000 [metadata-store-10-1] INFO  org.apache.pulsar.metadata.bookkeeper.PulsarRegistrationClient - Bookie main-bk-2:3181 disappeared","main-broker-1"
"Jun 16, 2023 @ 16:33:35.908","2023-06-16T16:33:35,908+0000 [metadata-store-10-1] INFO  org.apache.pulsar.metadata.bookkeeper.PulsarRegistrationClient - Bookie main-bk-2:3181 disappeared","main-broker-2"
"Jun 16, 2023 @ 16:33:35.908","2023-06-16T16:33:35,908+0000 [metadata-store-10-1] INFO  org.apache.pulsar.metadata.bookkeeper.PulsarRegistrationClient - Bookie main-bk-2:3181 disappeared","main-broker-0"
"Jun 16, 2023 @ 16:33:35.908","2023-06-16T16:33:35,908+0000 [metadata-store-10-1] INFO  org.apache.pulsar.metadata.bookkeeper.PulsarRegistrationClient - Bookie main-bk-2:3181 disappeared","main-broker-2"
"Jun 16, 2023 @ 16:33:35.908","2023-06-16T16:33:35,908+0000 [metadata-store-10-1] INFO  org.apache.pulsar.metadata.bookkeeper.PulsarRegistrationClient - Bookie main-bk-2:3181 disappeared","main-broker-0"

From the logs above, you can understand that some updates were lost in some broker's.

What did you expect to see?

No bookie information is missing.

What did you see instead?

Some bookie information has been missed.

Anything else?

No response

Are you willing to submit a PR?

• I'm willing to submit a PR!