Can't serialize message of type "pulsar.proto.MessageMetadata" because it is missing required fields: (cannot determine missing fields for lite message)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp, javascript, nodejs
- Domain
- backend, distributed-systems
Research direction
Start by reproducing the producer restart with Node.js 16, pulsar-client 1.6.2, and a Pulsar 2.7 cluster, then trace native serialization of pulsar.proto.MessageMetadata around the reported libprotobuf failure. Done means identifying why required fields are missing and confirming that producer restart no longer terminates with the fatal exception.
Written by the indexing model from the issue text.
Description
nodejs 16
sdk version：nodejs pulsar-client 1.6.2
cluster version 2.7
When I restart the producer, I get the following error：
2022-07-12 12:54:07.697 INFO [140305944786688] HTTPLookupService:295 | parsePartitionData = { LookupDataResult [brokerUrl_ = ] [brokerUrlTls_ = ] [partitions = 2] [authoritative = 0] [redirect = 0] proxyThroughServiceUrl = 0] }
[libprotobuf FATAL google/protobuf/message_lite.cc:327] CHECK failed: IsInitialized(): Can't serialize message of type "pulsar.proto.MessageMetadata" because it is missing required fields: (cannot determine missing fields for lite message)
terminate called after throwing an instance of 'google::protobuf::FatalException'
what(): CHECK failed: IsInitialized(): Can't serialize message of type "pulsar.proto.MessageMetadata" because it is missing required fields: (cannot determine missing fields for lite message)
Why is there such an error, is it a bug?
- Dominant language
- C++
- Stars
- 164
- Forks
- 99
- Avg merge
- 5d 18h
- Merged PRs (30d)
- 2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/pulsar-client-node
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
apache/pulsar-client-node#477 ·
-
公司网络无法访问海外站点，如何解决？ Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
apache/pulsar-client-node#455 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
apache/pulsar-client-node#432 · 2 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
apache/pulsar-client-node#431 · 3 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
apache/pulsar-client-node#429 · 1 comment ·
All issues in apache/pulsar-client-node
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·