Filtered replication failure on changes_timeout
I have a filtered replication routine that always fails with the error message showing "changes_timeout". Without filters it works fine, though. I may not have understood this correctly, but I think this indicates that the filter is running too long causing the destination server to not send a heartbeat signal, thus triggering the timeout? My database is rather large with upwards of 10k documents.
I also notice that on replication, the changes heartbeat is set to 10 secs. Is there any way to change this value through either configuration or query string? Or is the heartbeat value irrelevant to the problem I'm having?
Any suggestions are welcome.