Return-Path: Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: (qmail 60537 invoked from network); 5 Nov 2009 13:21:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 5 Nov 2009 13:21:29 -0000 Received: (qmail 93810 invoked by uid 500); 5 Nov 2009 13:21:27 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 93755 invoked by uid 500); 5 Nov 2009 13:21:27 -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 93745 invoked by uid 99); 5 Nov 2009 13:21:27 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Nov 2009 13:21:27 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of avlesh@gmail.com designates 209.85.222.173 as permitted sender) Received: from [209.85.222.173] (HELO mail-pz0-f173.google.com) (209.85.222.173) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Nov 2009 13:21:17 +0000 Received: by pzk3 with SMTP id 3so5134182pzk.20 for ; Thu, 05 Nov 2009 05:20:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=B6SDZa6ygtROoFeje4MTesR19wv8v89at2lPr+vNK38=; b=s7/3YUyr40SgKKe+NKDYrYjAKKGuZdyylXKcf0o4GlhK14MstcBDP9Je/to8Qa6a4P ezd2rYBs26OsqVB/OzOBUIhUSmu8f+isWbIwrHSfE8WJDME01woe75ZH2mpJo/UfjXgI UZ95VliU42ZJrM2bYGnbI8i4n3pnd0kR7ADdw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=hhgytwwuXehff6QjsB9fX+gxuAJ8/r/uOIBCSMQQG9Hppn91n7WNaMEMxvcBcGF6U8 1oU/6izKtrrYWvFXTlvWXekdhjFJC2Igl/3cETsnN1jh1T0ksGfg1vdI62WUZIJN6CYB 4LD2dfTePFgQ01s0s1CVUy1+PnNLXZxHYAHaw= MIME-Version: 1.0 Received: by 10.143.27.41 with SMTP id e41mr310098wfj.218.1257427256066; Thu, 05 Nov 2009 05:20:56 -0800 (PST) In-Reply-To: <26213642.post@talk.nabble.com> References: <26213642.post@talk.nabble.com> Date: Thu, 5 Nov 2009 18:50:56 +0530 Message-ID: Subject: Re: DIH full-import with fetchSize(Integer.MIN_VALUE) taking long time to start processing rows From: Avlesh Singh To: solr-user@lucene.apache.org Content-Type: multipart/alternative; boundary=00504502cd11edc2d504779f98be X-Virus-Checked: Checked by ClamAV on apache.org --00504502cd11edc2d504779f98be Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable > > Parallelly I have another process wich is doing lots of inserts to that > table (I also had it before but with less number of inserts). Could this = be > causing some bloking that makes the query take that long? In case not, an= d > advice what could make to take so long until I start see rows beeing > processed? > Sounds scary! With innodb engine you are causing a table level lock with each insert (assuming your table has an auto-increment column). With frequent inserts you are of-course delaying the read time. Why would you want to do this kind of an operation in the very first place? Can't you use views for indexing? Cheers Avlesh On Thu, Nov 5, 2009 at 6:18 PM, Marc Sturlese wrot= e: > > I have been using fetchSize(Integer.MIN_VALUE) for a long time and it was > working perfect until now. I use MySQL, java 1.6, > mysql-connector-java-5.1.7-bin.jar and InoDB tables. > Since a month ago when the query is executed it will take a long time > untill > it starts processing the results from the resultSet. The query matches > about > 2M rows. It use to take 10 min untill rows processing started. Now it=92s > taking about 2 hours. > Parallelly I have another process wich is doing lots of inserts to that > table (I also had it before but with less number of inserts). Could this = be > causing some bloking that makes the query take that long? In case not, an= d > advice what could make to take so long until I start see rows beeing > processed? > Thanks in advance. > -- > View this message in context: > http://old.nabble.com/DIH-full-import-with-fetchSize%28Integer.MIN_VALUE%= 29-taking-long-time-to-start-processing-rows-tp26213642p26213642.html > Sent from the Solr - User mailing list archive at Nabble.com. > > --00504502cd11edc2d504779f98be--