seigel/pouchdb-react-native

Aborting when replicate localdb to remote db 6.4.3 but pull is working (Replication Local to remote Not Working )

vjijardar opened this issue · 4 comments

Hello,
I'm using PRN - 6.4.3
the issue is when i'm changing the localdb and start the Pouchdb.replicate(localdb,remotedb) so i'm always getting ETIMEOUT and Doc not pushed on couchbase server.

Pouchdb 6.4.3
couchbase server : Enterprise Edition 5.0.1 build 5003
sync gateway : 2.0.0

{"code":"ETIMEDOUT","status":0,"result":{"ok":false,"start_time":"2018-09-27T06:10:22.869Z","docs_read":0,"docs_written":0,"doc_write_failures":0,"errors":[],"status":"aborting","end_time":"2018-09-27T06:10:24.583Z","last_seq":0}}

pouchdb:api http://xxxx.xxxx.in:4984/profile +132ms id error Error: ETIMEDOUT
at XMLHttpRequest.xhr.onreadystatechange (C:\Users\admin\Desktop\DigirecordsLite\node_modules\pouchdb-ajax\lib\index-browser.js:221)
at XMLHttpRequest.dispatchEvent (C:\Users\admin\Desktop\DigirecordsLite\node_modules\event-target-shim\lib\event-target.js:172)
at XMLHttpRequest.setReadyState (C:\Users\admin\Desktop\DigirecordsLite\node_modules\react-native\Libraries\Network\XMLHttpRequest.js:559)
at XMLHttpRequest.abort (C:\Users\admin\Desktop\DigirecordsLite\node_modules\react-native\Libraries\Network\XMLHttpRequest.js:541)
at timeoutReq (C:\Users\admin\Desktop\DigirecordsLite\node_modules\pouchdb-ajax\lib\index-browser.js:125)
at C:\Users\admin\Desktop\DigirecordsLite\node_modules\react-native\Libraries\Core\Timers\JSTimers.js:256
at _callTimer (C:\Users\admin\Desktop\DigirecordsLite\node_modules\react-native\Libraries\Core\Timers\JSTimers.js:152)
at Object.callTimers (C:\Users\admin\Desktop\DigirecordsLite\node_modules\react-native\Libraries\Core\Timers\JSTimers.js:405)
at MessageQueue.__callFunction (C:\Users\admin\Desktop\DigirecordsLite\node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:351)
at C:\Users\admin\Desktop\DigirecordsLite\node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:116

Did you solve this?

@d4rth-v4d3r the issue is not solved yet due to the Pouchdb has not supported the couchbase sync gateway so we move ahead and migrate our DB.

Does this happen also for Apache CouchDb?

It's Working fine with Couchdb.