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 C3CDC92AE for ; Thu, 2 Feb 2012 13:30:48 +0000 (UTC) Received: (qmail 63714 invoked by uid 500); 2 Feb 2012 13:30:45 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 63635 invoked by uid 500); 2 Feb 2012 13:30:44 -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 63627 invoked by uid 99); 2 Feb 2012 13:30:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Feb 2012 13:30:44 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [74.125.82.48] (HELO mail-ww0-f48.google.com) (74.125.82.48) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Feb 2012 13:30:38 +0000 Received: by wgbdq13 with SMTP id dq13so1828090wgb.5 for ; Thu, 02 Feb 2012 05:30:16 -0800 (PST) MIME-Version: 1.0 Received: by 10.180.92.227 with SMTP id cp3mr4599546wib.13.1328189416082; Thu, 02 Feb 2012 05:30:16 -0800 (PST) Received: by 10.216.192.214 with HTTP; Thu, 2 Feb 2012 05:30:16 -0800 (PST) Date: Thu, 2 Feb 2012 11:30:16 -0200 Message-ID: Subject: solr taking too long to update a document From: Carlos Alberto Schneider To: solr-user@lucene.apache.org Content-Type: multipart/alternative; boundary=f46d043bdefc570de504b7fb32dc --f46d043bdefc570de504b7fb32dc Content-Type: text/plain; charset=ISO-8859-1 Good morning everyone, I'm working on a project using solr 3.5, one master and two slaves. We run a grails app, and it has an update function. When the user click the button, we search for the message to be updated, clone it using SolrJ, delete the old message and save the new one. We do this update both on master and slave. The grails app uses the slave solr to get the data that will be displayed to the *users. **Problem:* It's taking too long till the users can see the updated message, *around 30 seconds. * So, If the users reload the page, it seems an error. If we do this change only on the master, it takes yet more time cause we must wait for the sync(every 3 seconds). We have 37GB(30 million docs) of data. If we could get 3 to 5 seconds, it would be acceptable. Any ideas? Thanks... -- Carlos Alberto Schneider Informant -(47) 38010919 - 9904-5517 --f46d043bdefc570de504b7fb32dc--