Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of yago.riveiro@gmail.com
 designates 209.85.216.181 as permitted sender)
Date: Fri, 07 Nov 2014 05:09:52 -0800 (PST)
MIME-Version: 1.0
Message-Id: <1415365792067.b9ad057c@Nodemailer>
In-Reply-To: <1415364281138-4168156.post@n3.nabble.com>
References: <1415364281138-4168156.post@n3.nabble.com>
From: "Yago Riveiro" <yago.riveiro@gmail.com>
To: solr-user@lucene.apache.org
Cc: solr-user@lucene.apache.org
Subject: Re: out of memory when trying to sort by id in a 1.5 billion index
Content-Type: multipart/alternative;
 boundary="----Nodemailer-0.5.0-?=_1-1415365792426"

------Nodemailer-0.5.0-?=_1-1415365792426
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

For sorting DocValues are the best option I think.

=E2=80=94
/Yago Riveiro

On Fri, Nov 7, 2014 at 12:45 PM, adfel70 <adfel70@gmail.com> wrote:

> hi
> I have 11 machines in my cluster.
> each machine 128GB memory, 2 solr jvm's with 12gb heap each.
> cluster has 7 shard, 3 replicas.
> 1.5 billion docs total.
> most user queries are pretty simple for now, sorting by date fields and
> another field the has around 1000 unique values.
> I have a usecase for using cursorpage and when tried to check this, I =
got
> outOfMemory just for sorting by id.
> I read in old posts that I should add heap memory, and I can do that, but=
 I
> would rather not .
> All other usecases I have are using stable 8gb heap .
> Any other way to handle this in solr 4.8=3F
> --
> View this message in context: http://lucene.472066.n3.nabble.=
com/out-of-memory-when-trying-to-sort-by-id-in-a-1-5-billion-index-tp416815=
6.html
> Sent from the Solr - User mailing list archive at Nabble.com.
------Nodemailer-0.5.0-?=_1-1415365792426--