Yes, you are right, maybe I can execute OPTIMIZE queries if job fails again, let's just cross fingers.
El jue., 9 ago. 2018 a las 12:28, Karl Wright (<[email protected]>) escribió: > There is no autovacuum for MySQL. MySQL apparently does dead tuple > cleanup as it goes. > > Karl > > On Thu, Aug 9, 2018 at 6:13 AM Gustavo Beneitez < > [email protected]> wrote: > >> Hi, >> >> looking at the manifoldCF pom I can see >> >> <version>1.0.4-SNAPSHOT</version> >> >> I'm not aware of any change in database, in fact ours is MySQL, I don't >> know if "auto_vacuum" property is present in MySQL installation. >> >> Thanks! >> >> El jue., 9 ago. 2018 a las 11:19, msaunier (<[email protected]>) >> escribió: >> >>> Hi Gustavo, >>> >>> >>> >>> What is your ManifoldCF version? >>> >>> Do you have disabled auto_vacuum on your SQL configuration? >>> >>> >>> >>> Maxence, >>> >>> >>> >>> >>> >>> >>> >>> *De :* Gustavo Beneitez [mailto:[email protected]] >>> *Envoyé :* jeudi 9 août 2018 11:17 >>> *À :* [email protected] >>> *Objet :* crawl interrupted >>> >>> >>> >>> Hi all, >>> >>> >>> >>> The Manifold crawler just aborted his jobs and recordeda message in job >>> status: >>> >>> >>> >>> Error: Unexpected jobqueue status - record id 1533799203323, expecting >>> active status, saw 2 >>> >>> >>> >>> Do you know what does it mean? Maybe I have to ask for GC or catalina >>> logs. >>> >>> >>> >>> Thanks! >>> >>
