Closed
Description
Hi, currently JDBCWriter will lose logs if a connection drops or before a connection is established.
Can a replay buffer be added to deal with these situations? i.e. check connection and reconnect if required, but do not "lose" these entries. Instead add it to a queue and write them again when connect is available.
Metadata
Metadata
Assignees
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
gabrielnasser commentedon Mar 22, 2019
Perhaps this could be done via the existing writing thread functionality by adding persistence to it? That way persistence can be enjoyed by any writer.
re-thc commentedon Apr 11, 2019
There's a slight difference. If persistence happens across the board - where does this go? In a file or JDBC? Which becomes a circular problem. A global buffer would be good though - even for file so we can log before it opens.
I think slf4j does something similar with a substitute logger that gets initialized at the start and then swaps over once the real logger initializes.
pmwmedia commentedon Jun 19, 2019
A pull request is welcome!
[-]Feature request: Buffer for JDBCWriter[/-][+]Feature request: Keep buffer of JdbcWriter after connection loss[/+][-]Feature request: Keep buffer of JdbcWriter after connection loss[/-][+]Keep buffer of JdbcWriter after connection loss[/+]pmwmedia commentedon Jan 26, 2022
Could be solved easily inside of JdbcWriter.java
Keep buffer of Jdbc writer after connection loss
github-actions commentedon Oct 9, 2022
This closed issue has been locked automatically.
However, please feel free to file a new issue.