Stef,
Yes, delete all index files, and usually you have to delete the directory as
well.
--j
On 2010-01-25, at 12:56 AM, stef25 wrote:
> Jayson,
>
> Assuming the index is corrupt - how can it be fixed? Delete all the index
> files?
>
> Thanks
> Stef
>
> On Sat, Jan 23, 2010 at 9:52 AM, Stefan Kendrew <[hidden email]> wrote:
>
> > Thanks for these suggestions.
> >
> > The site has about 5000 pages of content, I don't think we would have
> > reached some kind of limit. I think a corrupt index is a possible
> > reason since these files were restored from backup after a server
> > crash.
> >
> > Ill get back to you about this on monday when I have access to the files.
> >
> > Stef
> >
> > On Fri, Jan 22, 2010 at 6:17 PM, Jayson Minard (ZDZ) [via Zend
> > Framework Community] <[hidden email]> wrote:
> >> This error can also be reported from reading the .tii file and seeing that
> >> the index term count > 32bit value. Is there a chance your index is full
> >> of
> >> an incredible amount of unique terms?
> >>
> >> It could also be: a corrupt index.
> >>
> >> I *think* this is the only place that error is really reported in the
> >> Zend_Search_Lucene version.
> >>
> >> If you index is small enough, I could check it to be sure (if you are
> >> comfortable sharing it) -- or you can check it by opening it in the Java
> >> version as a comparison. Would be good to know if it is the index being
> >> corrupted, or a bug elsewhere. Although this is pretty simple code that
> >> reports the error so I'm betting on corrupt index or large number of
> >> unique
> >> terms as a backup guess.
> >>
> >> --j
> >>
> >> On 2010-01-22, at 3:18 AM, stef25 wrote:
> >>
> >>>
> >>> We run a ZF site that uses Lucene as the search engine. Recently it
> >>> stopped
> >>> working and the only message I can get the system to show is
> >>>
> >>> [message:protected] => Largest supported segment size (for 32-bit mode)
> >>> is
> >>> 2Gb
> >>>
> >>> However the site is a relatively small one and the indexes are nowhere
> >>> near
> >>> 2GB. I'm trying to optimize() the index via
> >>>
> >>> $index =
> >>> Zend_Search_Lucene::open('/www/site-name/staging/data/shopIndex');
> >>> $index->optimize();
> >>>
> >>> But the above error message is triggered by the first line, so I can't
> >>> get
> >>> to the optimize function. Does anyone know what causes this error (if the
> >>> index size is nowhere near 2GB) and how it could be fixed?
> >>> --
> >>> View this message in context:
> >>> http://n4.nabble.com/Zend-Search-Lucene-issue-tp1099952p1099952.html
> >>> Sent from the Zend Framework mailing list archive at Nabble.com.
> >>
> >>
> >> ________________________________
> >> View message @
> >> http://n4.nabble.com/Zend-Search-Lucene-issue-tp1099952p1103217.html
> >> To unsubscribe from Zend_Search_Lucene issue, click here.
> >>
> >
> >
> >
> > --
> > [hidden email]
> > phone: +32 479 825 931
> >
>
>
>
> --
> [hidden email]
> phone: +32 479 825 931
>
> View this message in context: Re: [fw-general] Zend_Search_Lucene issue
> Sent from the Zend Framework mailing list archive at Nabble.com.
