[ https://issues.apache.org/jira/browse/SOLR-12388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16497095#comment-16497095 ]
ASF subversion and git services commented on SOLR-12388: -------------------------------------------------------- Commit 114461cbeb2c7a2c9f610a46d4e01ca2ee9cf171 in lucene-solr's branch refs/heads/branch_7x from [~steve_rowe] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=114461c ] SOLR-12388: print out exception when assert fails > Enable a strict ZooKeeper-connected search request mode, in which search > requests will fail when the coordinating node can't communicate with ZooKeeper > ------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: SOLR-12388 > URL: https://issues.apache.org/jira/browse/SOLR-12388 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: search, SolrCloud > Reporter: Steve Rowe > Assignee: Steve Rowe > Priority: Minor > Fix For: 7.4, master (8.0) > > Attachments: SOLR-12388.patch > > > Right now, a Solr node will return the results of a search request even if it > cannot communicate with ZooKeeper at the time it receives the request. This > may result in stale or incorrect results if there have been major changes to > the collection structure that the node has not been informed of via > ZooKeeper. When this happens, as long as all known shards respond, the > response will succeed, and a {{zkConnected}} header set to {{false}} is > included in the search response. > There should be an option to instead fail requests under these conditions, to > prevent stale or incorrect results. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org