Details
-
Bug
-
Resolution: Duplicate
-
Major
-
2.3.3
-
None
-
1
Description
After a simple insert inside a Transaction context, a HUGE amount (every 1ms) of logs appears.
Sample log:
[cb-events] INFO com.couchbase.transactions.cleanup.lost - [com.couchbase.transactions.cleanup.lost][LogEvent] Client fa245 stop on CollectionIdentifier{bucket='myBucket', scope=Optional[_default], collection=Optional[_default], isDefault=true} = false
As we can see, even if the log is `INFO` level has two basic problems that prevent us for using it:
- The "com.couchbase.transactions.cleanup.lost" seems like a problem. Probably something is lost.
- Huge amount of logs that might affect performance.
The problem can be demonstrated here:
https://github.com/spirostz/couchbase-transactions/blob/main/src/test/java/org/spiros/CouchbaseTransactionsTest.java
see: Problem 3