(explicitly adding Utkarsh). On Wed, Nov 20, 2024 at 10:13 AM John Casey via user <user@beam.apache.org> wrote:
> Hi Utkarsh, > > I can't say for certain without more details, but timeouts against Kafka > usually represent auth issues. > > By and large, when a user tries to connect but doesn't have permission, > Kafka times out the connection instead of sending back a "not > authenticated/authorized" message. > > This can also happen if SSL configs don't align between the client and the > broker for much the same reason, which can sometimes happen because the > connection is happening from the worker machine, not from the machine that > submitted the Beam job. > > Usually this isn't networking per se, as if that were the case the client > would normally say that the bootstrap server is unresolvable. > > If you're still having trouble after investigating, I'd recommend > opening a support ticket with Google. > > Thanks, > John > > On Sun, Nov 17, 2024 at 5:59 PM Utkarsh Parekh < > utkarsh.par...@albertsons.com> wrote: > >> >> >> Hi Team, >> >> >> >> I’m facing an issue while fetching topic metadata from the Kafka cluster, >> resulting in the following exception. The metadata property is set to true >> in the ReadFromKafka KafkaIO transform: >> >> >> >> org.apache.kafka.common.errors.TimeoutException: Timeout expired while >> fetching topic metadata >> >> >> >> Any guidance on how to handle this exception would be greatly appreciated. >> >> >> >> Thank you, >> >> -- >> >> Utkarsh >> >> Sr. Data Engineer >> >> Albertsons Companies >> >> Mobile: (860)-578-5208 <(860)%20578-5208> >> >> Email: utkarsh.par...@albertsons.com >> ------------------------------ >> Warning: All e-mail sent to this address will be received by the >> corporate e-mail system, and is subject to archival and review by someone >> other than the recipient. This e-mail may contain proprietary information >> and is intended only for the use of the intended recipient(s). If the >> reader of this message is not the intended recipient(s), you are notified >> that you have received this message in error and that any review, >> dissemination, distribution or copying of this message is strictly >> prohibited. If you have received this message in error, please notify the >> sender immediately. >> ------------------------------ >> >
