You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 9, 2022. It is now read-only.
I am positive that my server is up and running on touchdb://server1/. Nevertheless, it seems that when I query touchdb://server1/_active_tasks through the REST protocol, I keep receiving timeouts. This only happens during my first connection to my app which does a lot of pulling from the cloud server through one continuous pull replication. I suspect that all the pulling might bottleneck the server, but it is hard to tell. Feel free to tell me what logging channels you need me to activate to help you resolve this.
The text was updated successfully, but these errors were encountered:
Capture a stack sample of the process while this is going on, and we can see whether the CouchDB thread is actually stuck somewhere. (You can do this with Instruments. Or a low-rent way to do it is just to pause the app and look at all the thread stacks.)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello,
I am positive that my server is up and running on
touchdb://server1/
. Nevertheless, it seems that when I querytouchdb://server1/_active_tasks
through the REST protocol, I keep receiving timeouts. This only happens during my first connection to my app which does a lot of pulling from the cloud server through one continuous pull replication. I suspect that all the pulling might bottleneck the server, but it is hard to tell. Feel free to tell me what logging channels you need me to activate to help you resolve this.The text was updated successfully, but these errors were encountered: