Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mongo Connection Timeouts #36

Open
jmrichardson opened this issue Jun 15, 2018 · 1 comment
Open

Mongo Connection Timeouts #36

jmrichardson opened this issue Jun 15, 2018 · 1 comment

Comments

@jmrichardson
Copy link

Hi,

I am using the Mongo crawlDataStoreFactory:

      <crawlDataStoreFactory
        class="com.norconex.collector.fs.data.store.impl.mongo.MongoCrawlDataStoreFactory">
        <host>localhost</host>
        <port>27017</port>
        <dbname>clients</dbname>
      </crawlDataStoreFactory>

Unfortunately, the connections to mongo sometimes are inactive (for some reason) which causes the crawler to stop and wait (indefinitely). This appears to happen at random times and I am not sure the root cause. If I restart Mongo, it closes the connections but the crawler also crashes as well. I am wondering if there is a way to put the maxIdleTimeout parameter into the Mongo connection string to avoid the hang:

https://docs.mongodb.com/manual/reference/connection-string/#maxIdleTimeMS

I am still investigating what is causing the issue. I am lowering the thread count to see if that helps as well. Thanks for your help

@essiembre
Copy link
Contributor

I am marking as a feature request. In the meantime, the filesystem collector should be able to resume where it stopped when you restart it (using the "resume" flag when starting it). You could use this to make sure you do not have to restart from the beginning.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants