[KAFKA-318] Improve HeartbeatManager logging Created: 22/Jun/22 Updated: 28/Oct/23 Resolved: 09/Aug/22 |
|
| Status: | Closed |
| Project: | Kafka Connector |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Unknown |
| Reporter: | Ross Lawley | Assignee: | Maxim Katcharov |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | Extended debugging for Kafka Connector |
| Description |
|
Currently, its not possible to determine the reason why the heartbeat manager does not produce heartbeats. Just get the following logs:
It would be good to understand if that is because of configuration, lack of a cursor or the same resumetoken. |
| Comments |
| Comment by Githook User [ 09/Aug/22 ] |
|
Author: {'name': 'Maxim Katcharov', 'email': 'maxim.katcharov@mongodb.com', 'username': 'katcharov'}Message: Log the reason why the heartbeat manager does not produce heartbeats (#115) Refactor and consolidate heartbeat creation logic
|