"cannot set inq fd=210 errno=92" isn't an error message but a debug message. setsockopt in the code may or may not succeed depending on the underlying kernel support. Presumably it isn't supported when running in a Kubernetes cluster.
On Monday, March 2, 2020 at 7:56:05 AM UTC-8 darren...@unity3d.com wrote: > We're debugging an issue which occurs only when our gRPC service is > running in a Kubernetes cluster (behind GCP LB & NGINX Ingress), but not in > a standalone container (in GCE). > > One thing we're seeing is a number of these errors: > > D0228 02:48:47.380209 140008409261824 > /var/local/git/grpc/src/core/lib/iomgr/tcp_posix.cc:1258: cannot set inq > fd=210 errno=92 > > Whilst I've found the origin of INQ > <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b75eba76d3d72e2374fac999926dafef2997edd2> > > and the source of that error message > <https://github.com/grpc/grpc/blob/master/src/core/lib/iomgr/tcp_posix.cc#L1812> > > in the gRPC code, that doesn't yet get me closer to understanding the > underlying issue (or if this is related to the actual cause of failure). > > Would it be possible to get further explanation on why this error might > occur? > > Thank you > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/ca6fb521-786a-49ea-b439-6e0f4accd93bn%40googlegroups.com.
