Return-Path: X-Original-To: apmail-lucene-solr-user-archive@minotaur.apache.org Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1BF9017733 for ; Tue, 28 Apr 2015 16:14:00 +0000 (UTC) Received: (qmail 88835 invoked by uid 500); 28 Apr 2015 16:13:56 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 88769 invoked by uid 500); 28 Apr 2015 16:13:56 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 88757 invoked by uid 99); 28 Apr 2015 16:13:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Apr 2015 16:13:55 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: message received from 54.76.25.247 which is an MX secondary for solr-user@lucene.apache.org) Received: from [54.76.25.247] (HELO mx1-eu-west.apache.org) (54.76.25.247) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Apr 2015 16:13:29 +0000 Received: from mail-qk0-f180.google.com (mail-qk0-f180.google.com [209.85.220.180]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 2022927FDD for ; Tue, 28 Apr 2015 16:13:28 +0000 (UTC) Received: by qkhg7 with SMTP id g7so82798897qkh.2 for ; Tue, 28 Apr 2015 09:13:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=CcD5MU5flDeaSlj+QntlybIkvCylWhq9OSwwIMFYklQ=; b=Ab6TNKeKV5FGdPMknNWpCEK053PVzaw+2BM8gXYlTX5K7KNlNHN13cDBiL8gkZ+wiK dftFql7FTnVeYczWSnExav5TNbP980QxFPCRh1HISzJg0TacrnaA0OQgKtnCafOUunAf kHybkM5lb6VLrvC0y8pOdVQgzGXgy+tFlCG6sjZz9AaHhK9aYJUxHFIbSlRy4ezcl1VE 84pse4AI7N9udxEL4tm5C+vtQWVCUnmjZ66YrSM7i/12VxUA8K4tTi0IQ6hjqmLMyUYW 6F7M/VIOENpsRrcsUt2x2dI4qoj+/XACtJTTxeNepeUqYKu7OnFD8/xU+1eynnjAED4a C8CQ== X-Gm-Message-State: ALoCoQljb4ysLjgmqzHb7Ax5A5sn/IaCPs2WFpo+VD5qpePuR0Z663hcmDDCGpH+RQVpraUhFQbk X-Received: by 10.55.20.159 with SMTP id 31mr20708904qku.64.1430237606911; Tue, 28 Apr 2015 09:13:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.96.170.74 with HTTP; Tue, 28 Apr 2015 09:13:05 -0700 (PDT) In-Reply-To: References: From: Ian Rose Date: Tue, 28 Apr 2015 12:13:05 -0400 Message-ID: Subject: Re: Async deleteshard commands? To: solr-user Content-Type: multipart/alternative; boundary=001a113b0bfe8137280514cb245a X-Virus-Checked: Checked by ClamAV on apache.org --001a113b0bfe8137280514cb245a Content-Type: text/plain; charset=UTF-8 Done! https://issues.apache.org/jira/browse/SOLR-7481 On Tue, Apr 28, 2015 at 11:09 AM, Shalin Shekhar Mangar < shalinmangar@gmail.com> wrote: > This is a bug. Can you please open a Jira issue? > > On Tue, Apr 28, 2015 at 8:35 PM, Ian Rose wrote: > > > Is it possible to run DELETESHARD commands in async mode? Google > searches > > seem to indicate yes, but not definitively. > > > > My local experience indicates otherwise. If I start with an async > > SPLITSHARD like so: > > > > > > > http://localhost:8983/solr/admin/collections?action=splitshard&collection=2Gp&shard=shard1_0_0&async=12-foo-1 > > > > Then I get back the expected response format, with > > 12-foo-1 > > > > And I can later query for the result via REQUESTSTATUS. > > > > However if I try an async DELETESHARD like so: > > > > > > > http://localhost:8983/solr/admin/collections?action=deleteshard&collection=2Gp&shard=shard1_0_0&async=12-foo-4 > > > > The response includes the command result, indicating that the command was > > not run async: > > > > > > > > > > 0 > > 16 > > > > > > > > > > And in addition REQUESTSTATUS calls for that requestId fail with "Did not > > find taskid [12-foo-4] in any tasks queue". > > > > Synchronous deletes are causing problems for me in production as they are > > timing out in some cases. > > > > Thanks, > > Ian > > > > > > p.s. I'm on version 5.0.0 > > > > > > -- > Regards, > Shalin Shekhar Mangar. > --001a113b0bfe8137280514cb245a--