[
https://issues.apache.org/jira/browse/KUDU-3154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150477#comment-17150477
]
Andrew Wong commented on KUDU-3154:
-----------------------------------
Re: the logging, the ordering can be explained by the fact that we're logging
from multiple threads, e.g.
MR: puts the message on the inbound queue
MP: takes the message from the inbound queue
MP: logs that the message was taken from the inbound queue
MR: logs that the message was put on the inbound queue
I've looked around a bit for issues with BlockingQueues, but at least the above
sequence explains it.
Then the question is, what's the subprocess doing for the rest of the time?
Still haven't been able to repro on my machine. I'll try on a dist-test
machine, since that's where we're seeing the issue fairly consistently.
> RangerClientTestBase.TestLogging sometimes fails
> ------------------------------------------------
>
> Key: KUDU-3154
> URL: https://issues.apache.org/jira/browse/KUDU-3154
> Project: Kudu
> Issue Type: Bug
> Components: ranger, test
> Affects Versions: 1.13.0
> Reporter: Alexey Serbin
> Priority: Major
> Attachments: ranger_client-test.txt.xz
>
>
> The {{RangerClientTestBase.TestLogging}} scenario of the
> {{ranger_client-test}} sometimes fails (all types of builds) with error
> message like below:
> {noformat}
> src/kudu/ranger/ranger_client-test.cc:398: Failure
> Failed
>
> Bad status: Timed out: timed out while in flight
>
> I0620 07:06:02.907177 1140 server.cc:247] Received an EOF from the
> subprocess
> I0620 07:06:02.910923 1137 server.cc:317] get failed, inbound queue shut
> down: Aborted:
> I0620 07:06:02.910964 1141 server.cc:380] outbound queue shut down: Aborted:
>
> I0620 07:06:02.910995 1138 server.cc:317] get failed, inbound queue shut
> down: Aborted:
> I0620 07:06:02.910984 1139 server.cc:317] get failed, inbound queue shut
> down: Aborted:
> {noformat}
> The log is attached.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
