Kafka:“经纪人未能验证记录”在增加分区之后

发布于 2025-02-12 00:33:24 字数 631 浏览 2 评论 0原文

我通过Terraform增加了现有的Kafka主题的分区。分区尺寸成功增加了,但是当我测试与该主题的连接时,我会得到一个“经纪人无法验证记录”

测试方法:

 echo "test" | kcat -b ...
**sensitive content has been removed**
...

% Auto-selecting Producer mode (use -P or -C to override)
% Delivery failed for message: Broker: Broker failed to validate record

我试图在线搜索并遇到了一些称为schema验证配置的东西: https://docs.confluent.io/cloud/cloud/current/current/sr /broker-side-schema-validation.html

增加分区后我需要做些什么? IE冲洗一些缓存?

I had increased the partition of an existing Kafka topic via terraform. The partition size had increased successfully however when I test the connection to the topic, I'm getting a "Broker failed to validate record"

Testing method:

 echo "test" | kcat -b ...
**sensitive content has been removed**
...

% Auto-selecting Producer mode (use -P or -C to override)
% Delivery failed for message: Broker: Broker failed to validate record

I had tried to search up online and came across something called schema validation configuration: https://docs.confluent.io/cloud/current/sr/broker-side-schema-validation.html

Is there something I need to do after increasing the partition? ie flush some cache?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

入怼 2025-02-19 00:33:24

您需要询问Kafka群集管理员是否已启用了模式验证,但是增加的分区不应引起这一点。 (这是Confluent服务器的功能,而不是Apache Kafka)。

如果有人更改了您的主题架构注册表中的架构,或者突然启用了验证,并且您正在从“旧”模式(或不正确的模式)发送记录,那么经纪人将“无法验证”记录。

You need to ask your Kafka cluster administrator if they have schema validation enabled, but increasing partitions shouldn't cause that. (This is a feature of Confluent Server, not Apache Kafka).

If someone changed the schema in the schema registry for your topic, or validation has suddenly been enabled, and you are sending a record from an "old" schema (or not correct schema), then the broker would "fail to validate" the record.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文