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
When not using load or one and syncing changes, every document will have its Seq (last since) written to the Mapping in elastic. This is to ensure sync can pick up where it left off. However from documentation it became clear that updating the mapping causes elastic to re-index the entire index every time the mapping is updated. We have been having serious elastic performance issues running tens of syncs on very large indexes. So I'm assuming this could be the cause.
With this and the related issue where template urls cannot be used with Sync, we are getting stuck with this library. I'm going to fork and change to save the Seq in a specific elastic index. I'm also going to add a key and use the CouchDB database and server as the key + custom key to save the Seq. This solves this issue, the URL Template issue and allows a user to have multiple instances of sync running from the same couchdb still. I'll also make it optional to keep backwards compatibility.
I'll pull when done. Leme know if there is a better idea.
The text was updated successfully, but these errors were encountered:
When not using load or one and syncing changes, every document will have its Seq (last since) written to the Mapping in elastic. This is to ensure sync can pick up where it left off. However from documentation it became clear that updating the mapping causes elastic to re-index the entire index every time the mapping is updated. We have been having serious elastic performance issues running tens of syncs on very large indexes. So I'm assuming this could be the cause.
With this and the related issue where template urls cannot be used with Sync, we are getting stuck with this library. I'm going to fork and change to save the Seq in a specific elastic index. I'm also going to add a key and use the CouchDB database and server as the key + custom key to save the Seq. This solves this issue, the URL Template issue and allows a user to have multiple instances of sync running from the same couchdb still. I'll also make it optional to keep backwards compatibility.
I'll pull when done. Leme know if there is a better idea.
The text was updated successfully, but these errors were encountered: