[
https://issues.apache.org/jira/browse/KUDU-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797689#comment-16797689
]
Adar Dembo commented on KUDU-2423:
----------------------------------
Saw this again:
{noformat}
[ RUN ] TestRpc.TestServerShutsDown
I0320 07:06:18.357066 223 rpc-test-base.h:597] Bound to: 0.0.0.0:42187
I0320 07:06:18.357116 223 rpc-test.cc:1003] Connecting to 0.0.0.0:42187
W0320 07:06:18.358333 232 negotiation.cc:313] Failed RPC negotiation. Trace:
0320 07:06:18.357731 (+ 0us) reactor.cc:583] Submitting negotiation task
for client connection to 0.0.0.0:42187
0320 07:06:18.357988 (+ 257us) negotiation.cc:98] Waiting for socket to
connect
0320 07:06:18.357997 (+ 9us) client_negotiation.cc:167] Beginning
negotiation
0320 07:06:18.358053 (+ 56us) client_negotiation.cc:244] Sending NEGOTIATE
NegotiatePB request
0320 07:06:18.358266 (+ 213us) negotiation.cc:304] Negotiation complete:
Network error: Client connection negotiation failed: client connection to
0.0.0.0:42187: BlockingRecv error: recv error from 0.0.0.0:0: Transport
endpoint is not connected (error 107)
Metrics:
{"client-negotiator.queue_time_us":202,"thread_start_us":42,"threads_started":1}
/data/somelongdirectorytoavoidrpathissues/src/kudu/src/kudu/rpc/rpc-test.cc:1074:
Failure
Value of: s.posix_code() == EPIPE || s.posix_code() == ECONNRESET ||
s.posix_code() == ESHUTDOWN || s.posix_code() == ECONNREFUSED || s.posix_code()
== EINVAL
Actual: false
Expected: true
Unexpected status: Network error: Client connection negotiation failed: client
connection to 0.0.0.0:42187: BlockingRecv error: recv error from 0.0.0.0:0:
Transport endpoint is not connected (error 107)
I0320 07:06:18.358696 223 test_util.cc:135]
-----------------------------------------------
I0320 07:06:18.358717 223 test_util.cc:136] Had fatal failures, leaving test
files at
/tmp/dist-test-taskJxf2XY/test-tmp/rpc-test.0.TestRpc.TestServerShutsDown.1553065575283406-223
[ FAILED ] TestRpc.TestServerShutsDown (2 ms)
{noformat}
> rpc-test flaky in TestRpc.TestServerShutsDown (ENOTCONN errno)
> --------------------------------------------------------------
>
> Key: KUDU-2423
> URL: https://issues.apache.org/jira/browse/KUDU-2423
> Project: Kudu
> Issue Type: Bug
> Components: rpc, test
> Affects Versions: 1.8.0
> Reporter: Todd Lipcon
> Priority: Major
>
> Seeing this flaky on the dashboard. errno seems to be getting set to ENOTCONN
> instead of one of the expected options:
> {code}
> 0430 03:18:29.804763 (+ 637us) negotiation.cc:304] Negotiation complete:
> Network error: Client connection negotiation failed: client connection to
> 0.0.0.0:35773: BlockingRecv error: recv error from 0.0.0.0:0: Transport
> endpoint is not connected (error 107)
> Metrics:
> {"client-negotiator.queue_time_us":382,"thread_start_us":187,"threads_started":1}
> /data/somelongdirectorytoavoidrpathissues/src/kudu/src/kudu/rpc/rpc-test.cc:989:
> Failure
> Value of: s.posix_code() == EPIPE || s.posix_code() == ECONNRESET ||
> s.posix_code() == ESHUTDOWN || s.posix_code() == ECONNREFUSED ||
> s.posix_code() == EINVAL
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
