Deleting zookeeper files did not help. I have huge postgresql db (~10G),
now it has ~30GB(a lot of dead rows), query are slow. I see many waiting commit 
query
and "UPDATE jobqueue SET docpriority=$1,priorityset=NULL WHERE jobid=$2".
I can only wait now.

K

On Tue, Nov 18, 2014 at 07:18:33AM -0500, Karl Wright wrote:
>    Please let me know if you were able to get past this.  MCF's database
>    states are quite resilient, so I'd be interested to see what kinds of
>    problems you have.
> 
>    Karl
> 
>    On Tue, Nov 18, 2014 at 6:21 AM, Karl Wright <[1][email protected]>
>    wrote:
> 
>      If you are using zookeeper, you may also want to purge the zookeeper
>      disk area as well, before starting any MCF processes.
> 
>      Karl
> 
>      On Tue, Nov 18, 2014 at 6:19 AM, Karl Wright <[2][email protected]>
>      wrote:
> 
>        Hi Kamil,
> 
>        I really don't know the failure modes of postgresql when it runs out
>        of disk space.  But if transactional integrity is maintained, it
>        should be sufficient to shut down all agents processes and start them
>        back up.
> 
>        Karl
> 
>        On Tue, Nov 18, 2014 at 4:24 AM, Kamil Żyta <[3][email protected]>
>        wrote:
> 
>          Hi,
>          I have problem with fixing manifoldcf after postgresql run without
>          disk space,
>          I resize postgresql partition x2 but when i start agents log is full
>          of:
> 
>          ERROR 2014-11-18 10:18:01,269 (Job reset thread) - Exception tossed:
>          Unexpected value for job status: 37
>          org.apache.manifoldcf.core.interfaces.ManifoldCFException:
>          Unexpected value for job status: 37
>                  at
>          org.apache.manifoldcf.crawler.jobs.Jobs.finishStopJob(Jobs.java:2973)
>                  at
>          
> org.apache.manifoldcf.crawler.jobs.JobManager.finishJobStops(JobManager.java:8236)
>                  at
>          
> org.apache.manifoldcf.crawler.system.JobResetThread.run(JobResetThread.java:69)
> 
>          is there a quick way to fix this without purge all postgresql db?
>          K
> 
> References
> 
>    Visible links
>    1. mailto:[email protected]
>    2. mailto:[email protected]
>    3. mailto:[email protected]

Reply via email to