eolivelli opened a new issue, #4326:
URL: https://github.com/apache/bookkeeper/issues/4326
**BUG REPORT**
***Describe the bug***
On the Bookie we log at ERROR level the LedgerFencedException in
BookieImpl.addEntry.
This is not actually a problem, it is not an ERROR in the bookie, it simply
means that some client is performing recovery and there is another client that
is trying to write to a fenced ledger.
We should not log this at ERROR level, that looks scary for system
administartors and also pollutes the logs
```
2024-05-22T22:11:13,669+0000 [bookie-io-8-6] ERROR
org.apache.bookkeeper.proto.WriteEntryProcessor - Attempt to write to fenced
ledger
org.apache.bookkeeper.bookie.BookieException$LedgerFencedException: null
at
org.apache.bookkeeper.bookie.BookieException.create(BookieException.java:57)
~[org.apache.bookkeeper-bookkeeper-server-4.16.5.jar]
at
org.apache.bookkeeper.bookie.BookieImpl.addEntry(BookieImpl.java:1071)
~[org.apache.bookkeeper-bookkeeper-server-4.16.5.jar]
at
org.apache.bookkeeper.proto.WriteEntryProcessor.processPacket(WriteEntryProcessor.java:79)
~[org.apache.bookkeeper-bookkeeper-server-4.16.5.]
```
***To Reproduce***
Steps to reproduce the behavior:
Write to a fenced ledger
***Expected behavior***
Only one line, at INFO level, reporting the ID of the ledger, and possibly
the client IP
***Additional context***
BookKeeper 4.16.5
--
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: commits-unsubscr...@bookkeeper.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
