[ https://issues.apache.org/jira/browse/SOLR-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16905618#comment-16905618 ]
ASF subversion and git services commented on SOLR-13464: -------------------------------------------------------- Commit 0291db44bc8e092f7cb2f577f0ac8ab6fa6a5fd7 in lucene-solr's branch refs/heads/master from Chris M. Hostetter [ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=0291db4 ] SOLR-13464: fix javadoc typo that precommit somehow missed? > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org