Hi,
I’ve just updated my Spring Boot application to v 2.1.0 a Couchbase server to v6.0.0. Now, every 30 seconds I’ve got this warning:
2018-11-05 16:55:02.724 WARN 1151 --- [cb-orphan-1] c.c.c.c.t.DefaultOrphanResponseReporter : Orphan responses observed: [{"top":[{"r":"172.31.7.30:8092","s":"view","c":"1FD2078F1B46396D/FFFFFFFFACEE92B2","l":"172.31.6.20:42556"}],"service":"view","count":1}]
What does it mean?
Thanks.
That is from the new Response Time Observability feature underlying the Java SDK. It would seem to indicate that you have view requests which are timing out, but eventually received later. Somewhere else in your app, something is timing out.
Have a look at the documentation for details.
It’d be worth investigating what the timeout is impacted by. You might be able to add resources/change your view request (stale=update_after instead of stale=false) to avoid the timeout or if it’s just a lot of work, increase the timeout value.
In any case, it’s indicative of an issue elsewhere in your app. The client is getting a response from the cluster, but the thread of execution that requested it has moved on.
I have only three views and there isn’t any read activity.
Server is mostly idle but warnings keep showing.
I have the same warnings:
2019-04-10 02:18:45 WARN DefaultOrphanResponseReporter:150 - Orphan responses observed: [{“top”:[{“r”:“10.233.95.97:8092”,“s”:“view”,“c”:“48E2C23AD82B02B5/0000000008367158”,“l”:“10.233.90.134:53862”},{“r”:“10.233.95.97:8092”,“s”:“view”,“c”:“48E2C23AD82B02B5/FFFFFFFFA20E5519”,“l”:“10.233.90.134:53844”},{“r”:“10.233.95.97:8092”,“s”:“view”,“c”:“48E2C23AD82B02B5/00000000789CA9E1”,“l”:“10.233.90.134:53866”},{“r”:“10.233.95.97:8092”,“s”:“view”,“c”:“48E2C23AD82B02B5/0000000037565334”,“l”:“10.233.90.134:53858”},{“r”:“10.233.95.97:8092”,“s”:“view”,“c”:“48E2C23AD82B02B5/FFFFFFFFCA351E6E”,“l”:“10.233.90.134:53852”},{“r”:“10.233.95.97:8092”,“s”:“view”,“c”:“48E2C23AD82B02B5/FFFFFFFFDB5AC896”,“l”:“10.233.90.134:53854”},{“r”:“10.233.95.97:8092”,“s”:“view”,“c”:“48E2C23AD82B02B5/0000000021A92621”,“l”:“10.233.90.134:53868”},{“r”:“10.233.69.84:8092”,“s”:“view”,“c”:“48E2C23AD82B02B5/0000000006FEB65B”,“l”:“10.233.90.134:37148”},{“r”:“10.233.69.84:8092”,“s”:“view”,“c”:“48E2C23AD82B02B5/0000000046307E6E”,“l”:“10.233.90.134:37156”},{“r”:“10.233.69.84:8092”,“s”:“view”,“c”:“48E2C23AD82B02B5/000000005F6049BD”,“l”:“10.233.90.134:37160”}],“service”:“view”,“count”:40}]
I have no views. Couchbase version 6.0.0, client library: "com.couchbase.client" % "java-client" % "2.7.2". Running on Kubernetes cluster, 25% utilization.
I noticed that all indexer were “blinking red” on Couchbase Index tab. Logs refuse to tell anything about this. I started to re-create all indexes, some of them are already “green”, hopefully that was the problem. Buckets also refused any write operation.
This red-green thingie is not very helpful or technical. 
Everything works fine so far but still getting DefaultOrphanResponseReporter WARNs on service “view”. We have no views.
even if you have no views, the SDK connects to the view service on each data node and runs a health check regularly to see if it is still working properly. those are likely timed out health checks, so something in general might be off in your environment? Did you open 8092 correctly so the clients can connect to the cluster on that port?
I have exactly the same problem
@sandro_rey so you are saying you have no views defined, the orphans dumped are likely from the noop polling to keep the sockets alive. Is it possible to share DEBUG logs from your environment (maybe via private message here in the forums?)
