Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Logminer hangs where log switch happens #83

Open
sriramcms opened this issue Sep 10, 2020 · 4 comments
Open

Logminer hangs where log switch happens #83

sriramcms opened this issue Sep 10, 2020 · 4 comments
Assignees

Comments

@sriramcms
Copy link

Hi Erdem:

In my tests i notice this frequently. I start the kafka connect logminer , it keep capturing the inserts. After some time i shutoff of the table insert simulator. If if leave it for a long period without any traffic -- and then start sending inserts again I noticed that
i dont get any more notifications on the kafka-connect-logminer

I checked that the network socket is still in established state,

I also noticed everytime this happens the the v$log entry for the SCN "v$log where ? between FIRST_CHANGE# and NEXT_CHANGE#" is now no more CURRENT and is archived.

I dont know what might be happening but some log getting switched from online to archived may be causing it.

To fix it , I have to kill and restart the process and then it catches up. Any thoughts on this behavior ?

Thanks

Sriram C

@zhaoxiangyublzcat
Copy link

What is the oracle version you have the problem with?

@yascov
Copy link

yascov commented Nov 9, 2020

Hi Erdem:

In my tests i notice this frequently. I start the kafka connect logminer , it keep capturing the inserts. After some time i shutoff of the table insert simulator. If if leave it for a long period without any traffic -- and then start sending inserts again I noticed that
i dont get any more notifications on the kafka-connect-logminer

I checked that the network socket is still in established state,

I also noticed everytime this happens the the v$log entry for the SCN "v$log where ? between FIRST_CHANGE# and NEXT_CHANGE#" is now no more CURRENT and is archived.

I dont know what might be happening but some log getting switched from online to archived may be causing it.

To fix it , I have to kill and restart the process and then it catches up. Any thoughts on this behavior ?

Thanks

Sriram C

Hello Sriram,

We are facing the same issue. Did you solve it ?

Best regards
Yascov

@erdemcer
Copy link
Owner

Hi,
Could you please send your connector log file from start to kill ?
Thanks

@erdemcer erdemcer self-assigned this Nov 13, 2020
@sriramcms
Copy link
Author

Yascov:

I did not solve it. For now the only option was to detect and kill the process so that it starts again clean from the previous state.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants