rahulgulati89 commented on issue #12196:
URL: https://github.com/apache/iceberg/issues/12196#issuecomment-3200112551
I am facing kind of similar issue when i am using Kafka connector to sink
Protobuf serialized messages into Managed iceberg tables using Databricks Unity
Catalog. Specially on Production environment, I am seeing these forbidden token
warning messages in Kafka connect logs. I have checked this with Databricks
support team as well and they have mentioned that this issue occurs
specifically when the OAuth2 token is being refreshed. From the Databricks
side, they see a 400 Bad Request response code, which indicates a malformed
request. The request format is: POST /oidc/v1/token
From what i can see is that the connector does not support token refresh
behavior but connector is somehow sending a request with
`grant_type=refresh_token`. These warnings does not impact the data sinking but
cause retries per connector and also put memory pressure on our Production
Kafka Connect Cluster. On the other hand, We are running the same setup on our
dev environment but we dont see any such warnings appearing there and the
connectors were able to run fine and sink data as well.
Do you know why the same connector version/setup is throwing such warnings?
`2025-07-31 05:22:31,441] ERROR
[iceberg-sink-connector-party-client_info_renewal_event-log-v2|task-0]
WorkerSinkTask{id=iceberg-sink-connector-party-client_info_renewal_event-log-v2-0}
Task threw an uncaught and unrecoverable exception. Task is being killed and
will not recover until manually restarted. Error: Forbidden: Invalid Token
(org.apache.kafka.connect.runtime.WorkerSinkTask)
org.apache.iceberg.exceptions.ForbiddenException: Forbidden: Invalid Token`
Screenshot of the error is attached below.
<img width="1919" height="757" alt="Image"
src="https://github.com/user-attachments/assets/2d7e443a-8a53-4e28-bcb8-b071051c995b";
/>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
