TCP_NODELAY may not be available.

[nicolasnoble]

I've just found a Linux environment that doesn't support TCP_NODELAY. I don't think this should be a fatal error.

Removing return GRPC_ERROR_CREATE("Failed to set TCP_NODELAY"); from src/core/lib/iomgr/socket_utils_common_posix.c makes everything work fine.

Otherwise, we get that kind of error:

D0804 23:53:35.722648900    5923 connectivity_state.c:156]   SET: 0x7f7a0c000de8 subchannel: CONNECTING --> TRANSIENT_FAILURE [connect_failed] error=0x7f7a0c0014d0 {"created":"@1470380015.722622600","description":"Connect Failed","file":"src/core/ext/client_config/subchannel.c","file_line":638,"referenced_errors":[{"created":"@1470380015.722295700","description":"Failed to set TCP_NODELAY","file":"src/core/lib/iomgr/socket_utils_common_posix.c","file_line":206}]}

[hsaliak]

Could you please provide more details on the platform? Is it manylinux

[nicolasnoble]

That was Windows 10 running Ubuntu :)

[atesop]

@nicolasnoble Has that been solved on Windows 10 running Ubuntu now？

[techscientist]

@nicolasnoble @hsaliak @atesop Hi there! I actually have the same question, since I am also getting the same error when trying to run gRPC server for tensorflow distributed training on Windows Ubuntu. Any fixes available?

[stale]

This issue/PR has been automatically marked as stale because it has not had any update (including commits, comments, labels, milestones, etc) for 180 days. It will be closed automatically if no further update occurs in 1 day. Thank you for your contributions!