You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pinot.apache.org by Pinot Slack Email Digest <ap...@gmail.com> on 2022/04/03 02:00:25 UTC
Apache Pinot Daily Email Digest (2022-04-02)
### _#general_
**@saimadhavheblikar:** @saimadhavheblikar has joined the channel
**@ysuo:** Hi team, if two tables ingest the same Kafka topic, will they have
the same copy of data?
**@mayanks:** Yes, but not guaranteed to be synchronized, as they will consume
at independent rates
**@ysuo:** I see. Thanks.
**@ysuo:** What’s the best practice to set
stream.kafka.consumer.prop.auto.offset.reset? I haven’t found detailed info
about it. I set it smallest in case stream data lost. But I met a situation,
when I restarted the controller, pinot just stopped consuming data.
**@mayanks:** That is only for first time consuming, and not to recover from
offset corruption
**@mayanks:** Your situation might be because you had restarted kafka changing
the offset. Do you expect running into that in production?
### _#random_
**@saimadhavheblikar:** @saimadhavheblikar has joined the channel
### _#troubleshooting_
**@saimadhavheblikar:** @saimadhavheblikar has joined the channel
### _#pinot-k8s-operator_
**@xiangfu0:** Do you know how many controller/broker/servers you need?
**@xiangfu0:** For prod quality, typically you need to have at least 2 pods
per component and config node affinity to ensure all the pods are not
scheduled on the same node
### _#getting-started_
**@saimadhavheblikar:** @saimadhavheblikar has joined the channel
### _#kinesis_help_
**@aiyas.aboobakar:** @aiyas.aboobakar has joined the channel
### _#udf-type-matching_
**@aiyas.aboobakar:** @aiyas.aboobakar has joined the channel
### _#jobs_
**@aiyas.aboobakar:** @aiyas.aboobakar has joined the channel
\--------------------------------------------------------------------- To
unsubscribe, e-mail: dev-unsubscribe@pinot.apache.org For additional commands,
e-mail: dev-help@pinot.apache.org