Yonik Seeley-2 wrote:
>
> If you make further changes to the index and do a commit, you should
> see the space go down.
>
It worked. I added a bogus document using /update and then performed a
commit and now the files are down to 6MB.
http://.../core00/update?stream.body=%3Cadd%3E%3Cdoc%3E%3
Yonik Seeley-2 wrote:
>
> On Tue, Dec 29, 2009 at 1:23 PM, markwaddle wrote:
>> I have an index that used to have ~38M docs at 17.2GB. I deleted all but
>> 13K
>> docs using a delete by query, commit and then optimize. A "*:*" query now
>> returns 13K docs. The problem is that the files on dis
On Tue, Dec 29, 2009 at 1:23 PM, markwaddle wrote:
> I have an index that used to have ~38M docs at 17.2GB. I deleted all but 13K
> docs using a delete by query, commit and then optimize. A "*:*" query now
> returns 13K docs. The problem is that the files on disk are still 17.1GB in
> size. I expe
Hi Mark,
I can't help with reducing filesizes, but I'm curious...
What sort of documents were you storing, number of fields, average document
size, many dynamic fields or mainly all static?
It would be good to hear about a real-world large-scale index in terms of
response times, did the serve
I have an index that used to have ~38M docs at 17.2GB. I deleted all but 13K
docs using a delete by query, commit and then optimize. A "*:*" query now
returns 13K docs. The problem is that the files on disk are still 17.1GB in
size. I expected the optimize to shrink the files. Is there a way I can
