Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 9FAEB200B5A for ; Thu, 4 Aug 2016 10:15:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 9E48E160AAE; Thu, 4 Aug 2016 08:15:22 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id E5BFA160A7C for ; Thu, 4 Aug 2016 10:15:21 +0200 (CEST) Received: (qmail 18086 invoked by uid 500); 4 Aug 2016 08:15:20 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 18066 invoked by uid 99); 4 Aug 2016 08:15:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Aug 2016 08:15:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id B49072C0D5E for ; Thu, 4 Aug 2016 08:15:20 +0000 (UTC) Date: Thu, 4 Aug 2016 08:15:20 +0000 (UTC) From: "Varun Thacker (JIRA)" To: dev@lucene.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SOLR-9090) solrj CloudSolrClient: add directUpdatesToLeadersOnly support MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 04 Aug 2016 08:15:22 -0000 [ https://issues.apache.org/jira/browse/SOLR-9090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407382#comment-15407382 ] Varun Thacker commented on SOLR-9090: ------------------------------------- Hi Christine, Just curious - Why shouldn't directUpdatesToLeadersOnly be the default behaviour? If at a time of an update there are no leaders then won't the request fail anyways? > solrj CloudSolrClient: add directUpdatesToLeadersOnly support > ------------------------------------------------------------- > > Key: SOLR-9090 > URL: https://issues.apache.org/jira/browse/SOLR-9090 > Project: Solr > Issue Type: New Feature > Components: SolrJ > Reporter: Christine Poerschke > Assignee: Christine Poerschke > Priority: Minor > Fix For: 6.2, master (7.0) > > Attachments: SOLR-9090.patch, SOLR-9090.patch > > > solrj CloudSolrClient: add directUpdatesToLeadersOnly support > (Marvin Justice, Christine Poerschke) > Proposed change: > * Addition of a {{directUpdatesToLeadersOnly}} flag to allow clients to request that direct updates be sent to the shard leaders and only to the shard leaders. > Motivation: > * In a scenario where there is temporarily no shard leader the update request will 'fail fast' allowing the client to handle retry logic. > Related tickets: > * SOLR-6312 concerns the ((currently) no longer used) {{updatesToLeaders}} flag. The updatesToLeaders logic however appears to be slightly different from the proposed directUpdatesToLeadersOnly logic: {{updatesToLeaders}} indicates that sending to leaders is preferred but not mandatory whereas {{directUpdatesToLeadersOnly}} mandates sending to leaders only. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org