[ 
https://issues.apache.org/jira/browse/KAFKA-7529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16661078#comment-16661078
 ] 

Sönke Liebau commented on KAFKA-7529:
-------------------------------------

Hi [~kivaturi], I am fairly certain that there should not be a "normal" 
situation where this happens. However as this ticket stands there is a very 
limited amount of information to work with, nothing comes immediately to mind.

Some things you could look at / try are:
 * Anything in the Connect logs?
 * enable trace logging for the connector, every time it is polled you should 
at least see "Polling for new data" - anything after that will give a better 
idea of what is happening
 * Check the offsets topic (Robin explains how to do this 
[here|https://gist.github.com/rmoff/063e878f4ff0c0f8c09e9d8d15262c10] - I don't 
expect that you see anything here, but every bit of information help

 

> Kafka Connect JDBC doesn't push new records to Kafka Topic unless the 
> connector is restarted
> --------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-7529
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7529
>             Project: Kafka
>          Issue Type: Task
>          Components: KafkaConnect
>            Reporter: Kashyap Ivaturi
>            Priority: Major
>
> Hi,
> We have a Kafka Connect JDBC Source Connector which keeps polling for new 
> records in a Oracle table every minute and push the new records to Kafka 
> Topic. New records are determined by an incrementing column.
> In general everything works well but once in a while we see that even though 
> there were new records with incrementing column those records doesn't get 
> pushed to the Topic. There is no clue of any error in the logs and the 
> connector is in running state. Only after we restart the Connector the new 
> records are pushed to the Topic. 
> Any idea in what situation can this happen?. 
> Rgds
> Kashyap.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to