[ 
https://issues.apache.org/jira/browse/KUDU-3154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17155663#comment-17155663
 ] 

ASF subversion and git services commented on KUDU-3154:
-------------------------------------------------------

Commit 5291221ecea6b892364720342eb15c64bcf41e95 in kudu's branch 
refs/heads/master from Andrew Wong
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=5291221 ]

KUDU-3154: add policy to Ranger before authorizing

For whatever reason, in some environments, we've seen the Kudu Ranger
plugin hang when downloading policies. It isn't exactly clear why this
happens but one workaround we've seen is to add a policy to Ranger
before authorizing any requests. This patch adds the workaround to the
only Ranger test that suffers from this.

Change-Id: Ice0b3842335e5854835542e18b41c54509c2fc33
Reviewed-on: http://gerrit.cloudera.org:8080/16166
Reviewed-by: Alexey Serbin <aser...@cloudera.com>
Tested-by: Kudu Jenkins
Reviewed-by: Attila Bukor <abu...@apache.org>


> 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: kudu-3154_jstacks.txt, ranger_client-test.txt, 
> 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)

Reply via email to