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

ASF subversion and git services commented on SOLR-13464:
--------------------------------------------------------

Commit 06dd37e907df860125dbcaeb7a90ce5d7de684a1 in lucene-solr's branch 
refs/heads/branch_8x from Chris M. Hostetter
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=06dd37e ]

SOLR-13464: Test work arounds

 * Refactor existing work around in BasicAuthIntegrationTest up into 
SolrCloudAuthTestCase for re-use in JWTAuthPluginIntegrationTest

 * Simplify BasicAuthOnSingleNodeTest and PKIAuthenticationIntegrationTest to 
use their existing (static) security settings on creation of MiniSolrCloud.  
Since they no longer modify security.json once the nodes are alive, the issue 
no longer affects them

(cherry picked from commit c7822c393e6affa77c233f9e8e9bf9d8aeb12578)
(cherry picked from commit 0291db44bc8e092f7cb2f577f0ac8ab6fa6a5fd7)


> Sporadic Auth + Cloud test failures, probably due to lag in nodes reloading 
> security config
> -------------------------------------------------------------------------------------------
>
>                 Key: SOLR-13464
>                 URL: https://issues.apache.org/jira/browse/SOLR-13464
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Hoss Man
>            Priority: Major
>
> I've been investigating some sporadic and hard to reproduce test failures 
> related to authentication in cloud mode, and i *think* (but have not directly 
> verified) that the common cause is that after uses one of the 
> {{/admin/auth...}} handlers to update some setting, there is an inherient and 
> unpredictible delay (due to ZK watches) until every node in the cluster has 
> had a chance to (re)load the new configuration and initialize the various 
> security plugins with the new settings.
> Which means, if a test client does a POST to some node to add/change/remove 
> some authn/authz settings, and then immediately hits the exact same node (or 
> any other node) to test that the effects of those settings exist, there is no 
> garuntee that they will have taken affect yet.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to