I'm running a Spring Boot application that has a Couchbase DB.
In the application log, I see hundreds of records like that:
[cb-orphan-1] [31mWARN [0;39m [32mc.c.c.c.t.DefaultOrphanResponseReporter[0;39m - Orphan responses observed: [{"top":[{"r":"10.250.17.53:8092","s":"view","c":"13963D4B3G6AFE45/FFFFFFFF8F4D718C","l":"10.123.0.197:36530"}],"service":"view","count":1}
They differ from each other in the c value and they have different IP & port in the l value.
There is a time difference of few seconds between each of these log records.
After finding this post that suggested that somewhere else in the application there should be timeouts, I looked in the logs for such but didn't find any timeout errors.
- How can I know what was the query that resulted in that timeout?
- Is there a way to make this warning more verbose?
- What does the
"c":"13963D4B3G6AFE45/FFFFFFFF8F4D718C"stands for?
I have a similar problem. The logs show up even if the client stays completely idle.
OrphanResponseReporterimplementation.cstands forlast_local_id. According to the documentation (tracing-from-the-sdk.html), it can be used to correlate logs with server-side logs. Unfortunately, I was not able to do it.