# CouchDB \_river, ES failure and missing docs **URL:** \ **Category:** Elasticsearch\ **Created:** [December 18, 2012, 5:56pm UTC](https://discuss.elastic.co/t/couchdb--river-es-failure-and-missing-docs/10109 "2012-12-18T17:56:02Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![JP\_Toto](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jp_toto/32/2512_2.png) [@JP\_Toto](https://discuss.elastic.co/u/JP_Toto)\ **Post date:** [December 18, 2012, 5:56pm UTC](https://discuss.elastic.co/t/couchdb--river-es-failure-and-missing-docs/10109/1 "2012-12-18T17:56:02Z")
Hi all! Having an issue similar to [https://groups.google.com/forum/?fromgroups=#!searchin/elasticsearch/river$20missing/elasticsearch/Y8G4eu-sbrE/bNyopwUP\_kgJ](https://groups.google.com/forum/?fromgroups=#!searchin/elasticsearch/river%2420missing/elasticsearch/Y8G4eu-sbrE/bNyopwUP_kgJ) We had a node failure which we repaired and brought back up. ES re balanced itself and is all green (using 0.19.2). We're using the CouchDB river which generally works well. However, it missed some documents while we were down and now we have a gap that it doesn't' seem to be filling in. Is there a way to have the \_river re-scan \_changes or bootstrap it somehow? We're not sure how to get the gaps filled in. Thanks! -- ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [December 18, 2012, 5:59pm UTC](https://discuss.elastic.co/t/couchdb--river-es-failure-and-missing-docs/10109/2 "2012-12-18T17:59:13Z")
What you can probably do is to modify the meta data of the river. As far as I remember, you will find the latest change number that Elasticsearch process. You can update this particular document and set the field to xxxx (1 if you want to start from the begining). Does it help? David. Le 18 décembre 2012 à 18:56, JP Toto [james.p.toto@gmail.com](mailto:james.p.toto@gmail.com) a écrit : > Hi all! > > Having an issue similar to > [Redirecting to Google Groups](https://groups.google.com/forum/?fromgroups=#!searchin/elasticsearch/river$20missing/elasticsearch/Y8G4eu-sbrE/bNyopwUP_kgJ) > > We had a node failure which we repaired and brought back up. ES re balanced > itself and is all green (using 0.19.2). We're using the CouchDB river which > generally works well. However, it missed some documents while we were down and > now we have a gap that it doesn't' seem to be filling in. > > Is there a way to have the \_river re-scan \_changes or bootstrap it somehow? > We're not sure how to get the gaps filled in. > > Thanks! > > -- -- David Pilato [http://www.scrutmydocs.org/](http://www.scrutmydocs.org/) [http://dev.david.pilato.fr/](http://dev.david.pilato.fr/) Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs -- ---
**Author:** ![JP\_Toto](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jp_toto/32/2512_2.png) [@JP\_Toto](https://discuss.elastic.co/u/JP_Toto)\ **Post date:** [December 18, 2012, 6:09pm UTC](https://discuss.elastic.co/t/couchdb--river-es-failure-and-missing-docs/10109/3 "2012-12-18T18:09:15Z")
David, Thanks for the reply! Do you mean the the last\_seq field? Right now that looks like the below: If I set it to a previous id, will it dupe any documents that are after that? I don't mind overwriting documents but I don't want to duplicate any. Thanks for the help! - last\_seq: 109019340-g1AAAAXpeJyV1DssQ1EYB\_AbxGCXGCQGm0TjuUk0kXq03nxEDdKvtwlVvVLtym4zGMT7zdktFpsEs1liY\_N-FMf\_u1un5rvLf7m\_\_3nce07KcZyq6VLXqXU57mUSQZebA\_PeQnYulpltaGgMxFNezo2ls4F0IpvCyyUxhyuMOU2yE5qoU0lxhiuJRgT3Xukw3CjXWPsruL-mEDcVwXB\_XGfMseDucd3IcCfcSjQkOPijw3DD3G5tXnCUdRjuh8PGHAoevSzEjUUw3BET0YC\_29W6keEGecraL3\_kvA7DfXPSmH3Bg8rvDHfAOaI-weEb3Zrh-nnJ2g\_BkR3dyHCf6TJn15hlf-L1Kg65B4mIEK1KgRfVFvRCIt6s3ZaCtvvCgpaiBe-QiG0cNCkYftDOYAcS0UN0JgV9x9qCMCTixdoL\_6CeawteIRGbxlxLQceKdg-2IBFdRLdSMKS7pCC7IRFP1t75S1jUFjxDItaNefT\_w3JtwQYkIkT0JgVja6rbDrITEmHxSMHkTPIfOl4Kww } On Tuesday, December 18, 2012 12:59:13 PM UTC-5, David Pilato wrote: > What you can probably do is to modify the meta data of the river. As far > as I remember, you will find the latest change number that Elasticsearch > process. > You can update this particular document and set the field to xxxx (1 if > you want to start from the begining). > > Does it help? > > David. > > Le 18 décembre 2012 à 18:56, JP Toto \<[james....@gmail.com](mailto:james....@gmail.com) \\> > a écrit : > > Hi all! > > Having an issue similar to > [Redirecting to Google Groups](https://groups.google.com/forum/?fromgroups=#!searchin/elasticsearch/river$20missing/elasticsearch/Y8G4eu-sbrE/bNyopwUP_kgJ) > > We had a node failure which we repaired and brought back up. ES re > balanced itself and is all green (using 0.19.2). We're using the CouchDB > river which generally works well. However, it missed some documents while > we were down and now we have a gap that it doesn't' seem to be filling in. > > Is there a way to have the \_river re-scan \_changes or bootstrap it > somehow? We're not sure how to get the gaps filled in. > > Thanks! > > -- > > -- > David Pilato > [http://www.scrutmydocs.org/](http://www.scrutmydocs.org/) > [http://dev.david.pilato.fr/](http://dev.david.pilato.fr/) > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs -- ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [December 18, 2012, 6:16pm UTC](https://discuss.elastic.co/t/couchdb--river-es-failure-and-missing-docs/10109/4 "2012-12-18T18:16:50Z")
Yes. That's this field. Sounds like you are using a BigCouch instance, don't you? If so, you handle right now more than 100 millions changes, right? In that case, you have to find the right change id given by bigcouch. I think it's something like: xxxxxxx-BIGCOUCHADDON, where xxxxxxx is the real seq number in couchDb. David. Le 18 décembre 2012 à 19:09, JP Toto [james.p.toto@gmail.com](mailto:james.p.toto@gmail.com) a écrit : > David, > > Thanks for the reply! Do you mean the the last\_seq field? Right now that > looks like the below: If I set it to a previous id, will it dupe any documents > that are after that? I don't mind overwriting documents but I don't want to > duplicate any. > > Thanks for the help! > > ``` > * last_seq: > > ``` > > 109019340-g1AAAAXpeJyV1DssQ1EYB\_AbxGCXGCQGm0TjuUk0kXq03nxEDdKvtwlVvVLtym4zGMT7zdktFpsEs1liY\_N-FMf\_u1un5rvLf7m\_\_3nce07KcZyq6VLXqXU57mUSQZebA\_PeQnYulpltaGgMxFNezo2ls4F0IpvCyyUxhyuMOU2yE5qoU0lxhiuJRgT3Xukw3CjXWPsruL-mEDcVwXB\_XGfMseDucd3IcCfcSjQkOPijw3DD3G5tXnCUdRjuh8PGHAoevSzEjUUw3BET0YC\_29W6keEGecraL3\_kvA7DfXPSmH3Bg8rvDHfAOaI-weEb3Zrh-nnJ2g\_BkR3dyHCf6TJn15hlf-L1Kg65B4mIEK1KgRfVFvRCIt6s3ZaCtvvCgpaiBe-QiG0cNCkYftDOYAcS0UN0JgV9x9qCMCTixdoL\_6CeawteIRGbxlxLQceKdg-2IBFdRLdSMKS7pCC7IRFP1t75S1jUFjxDItaNefT\_w3JtwQYkIkT0JgVja6rbDrITEmHxSMHkTPIfOl4Kww > } > > On Tuesday, December 18, 2012 12:59:13 PM UTC-5, David Pilato wrote: > > > > What you can probably do is to modify the meta data of the river. As > > > far as I remember, you will find the latest change number that > > > Elasticsearch process. > > > You can update this particular document and set the field to xxxx (1 if > > > you want to start from the begining). > > > > Does it help? > > > > David. > > > > Le 18 décembre 2012 à 18:56, JP Toto \< [james....@gmail.com](mailto:james....@gmail.com)\> a écrit : > > > > ``` > > > > > Hi all! > > > > ``` > > > > > ``` > > > Having an issue similar to > > > > > > ``` > > > > > > [Redirecting to Google Groups](https://groups.google.com/forum/?fromgroups=#!searchin/elasticsearch/river$20missing/elasticsearch/Y8G4eu-sbrE/bNyopwUP_kgJ) > > > [https://groups.google.com/forum/?fromgroups=#!searchin/elasticsearch/river$20missing/elasticsearch/Y8G4eu-sbrE/bNyopwUP\_kgJ](https://groups.google.com/forum/?fromgroups=#!searchin/elasticsearch/river$20missing/elasticsearch/Y8G4eu-sbrE/bNyopwUP_kgJ) > > > > > > ``` > > > We had a node failure which we repaired and brought back up. ES re > > > > > > ``` > > > > > > balanced itself and is all green (using 0.19.2). We're using the CouchDB > > > river which generally works well. However, it missed some documents while > > > we were down and now we have a gap that it doesn't' seem to be filling in. > > > > > > ``` > > > Is there a way to have the _river re-scan _changes or bootstrap it > > > > > > ``` > > > > > > somehow? We're not sure how to get the gaps filled in. > > > > > > ``` > > > Thanks! > > > > > > -- > > > > > > > > > > > > -- > > > David Pilato > > > > > > > > > http://www.scrutmydocs.org/ > > > http://dev.david.pilato.fr/ > > > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > > > > > ``` > > > > > > > > > > > > -- > > > > > -- David Pilato [http://www.scrutmydocs.org/](http://www.scrutmydocs.org/) [http://dev.david.pilato.fr/](http://dev.david.pilato.fr/) Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs -- ---
**Author:** ![JP\_Toto](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jp_toto/32/2512_2.png) [@JP\_Toto](https://discuss.elastic.co/u/JP_Toto)\ **Post date:** [December 18, 2012, 6:20pm UTC](https://discuss.elastic.co/t/couchdb--river-es-failure-and-missing-docs/10109/5 "2012-12-18T18:20:37Z")
David, you're right about that! It's bigcouch - I forgot that detail 🙂 Thanks for the advice! We'll try this. On Tuesday, December 18, 2012 1:16:50 PM UTC-5, David Pilato wrote: > Yes. That's this field. Sounds like you are using a BigCouch instance, > don't you? If so, you handle right now more than 100 millions changes, > right? > > In that case, you have to find the right change id given by bigcouch. I > think it's something like: xxxxxxx-BIGCOUCHADDON, where xxxxxxx is the real > seq number in couchDb. > > David. > > Le 18 décembre 2012 à 19:09, JP Toto \<[james....@gmail.com](mailto:james....@gmail.com) \\> > a écrit : > > David, > > Thanks for the reply! Do you mean the the last\_seq field? Right now that > looks like the below: If I set it to a previous id, will it dupe any > documents that are after that? I don't mind overwriting documents but I > don't want to duplicate any. > > Thanks for the help! > > - last\_seq: > 109019340-g1AAAAXpeJyV1DssQ1EYB\_AbxGCXGCQGm0TjuUk0kXq03nxEDdKvtwlVvVLtym4zGMT7zdktFpsEs1liY\_N-FMf\_u1un5rvLf7m\_\_3nce07KcZyq6VLXqXU57mUSQZebA\_PeQnYulpltaGgMxFNezo2ls4F0IpvCyyUxhyuMOU2yE5qoU0lxhiuJRgT3Xukw3CjXWPsruL-mEDcVwXB\_XGfMseDucd3IcCfcSjQkOPijw3DD3G5tXnCUdRjuh8PGHAoevSzEjUUw3BET0YC\_29W6keEGecraL3\_kvA7DfXPSmH3Bg8rvDHfAOaI-weEb3Zrh-nnJ2g\_BkR3dyHCf6TJn15hlf-L1Kg65B4mIEK1KgRfVFvRCIt6s3ZaCtvvCgpaiBe-QiG0cNCkYftDOYAcS0UN0JgV9x9qCMCTixdoL\_6CeawteIRGbxlxLQceKdg-2IBFdRLdSMKS7pCC7IRFP1t75S1jUFjxDItaNefT\_w3JtwQYkIkT0JgVja6rbDrITEmHxSMHkTPIfOl4Kww > > } > > On Tuesday, December 18, 2012 12:59:13 PM UTC-5, David Pilato wrote: > > What you can probably do is to modify the meta data of the river. As far > as I remember, you will find the latest change number that Elasticsearch > process. > You can update this particular document and set the field to xxxx (1 if > you want to start from the begining). > > Does it help? > > David. > > Le 18 décembre 2012 à 18:56, JP Toto \< [james....@gmail.com](mailto:james....@gmail.com)\> a écrit : > > Hi all! > > Having an issue similar to > [Redirecting to Google Groups](https://groups.google.com/forum/?fromgroups=#!searchin/elasticsearch/river$20missing/elasticsearch/Y8G4eu-sbrE/bNyopwUP_kgJ) > > We had a node failure which we repaired and brought back up. ES re > balanced itself and is all green (using 0.19.2). We're using the CouchDB > river which generally works well. However, it missed some documents while > we were down and now we have a gap that it doesn't' seem to be filling in. > > Is there a way to have the \_river re-scan \_changes or bootstrap it > somehow? We're not sure how to get the gaps filled in. > > Thanks! > > -- > > [https://groups.google.com/forum/?fromgroups=#!searchin/elasticsearch/river$20missing/elasticsearch/Y8G4eu-sbrE/bNyopwUP\_kgJ](https://groups.google.com/forum/?fromgroups=#!searchin/elasticsearch/river$20missing/elasticsearch/Y8G4eu-sbrE/bNyopwUP_kgJ) > > -- > David Pilato > > [https://groups.google.com/forum/?fromgroups=#!searchin/elasticsearch/river$20missing/elasticsearch/Y8G4eu-sbrE/bNyopwUP\_kgJ](https://groups.google.com/forum/?fromgroups=#!searchin/elasticsearch/river$20missing/elasticsearch/Y8G4eu-sbrE/bNyopwUP_kgJ) > [http://www.scrutmydocs.org/](http://www.scrutmydocs.org/) > [http://dev.david.pilato.fr/](http://dev.david.pilato.fr/) > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > -- > > -- > David Pilato > [http://www.scrutmydocs.org/](http://www.scrutmydocs.org/) > [http://dev.david.pilato.fr/](http://dev.david.pilato.fr/) > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs -- ---
**Author:** ![JP\_Toto](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jp_toto/32/2512_2.png) [@JP\_Toto](https://discuss.elastic.co/u/JP_Toto)\ **Post date:** [December 18, 2012, 6:21pm UTC](https://discuss.elastic.co/t/couchdb--river-es-failure-and-missing-docs/10109/6 "2012-12-18T18:21:39Z")
Resetting the id won't dupe the subsequent docs in ES right? On Tuesday, December 18, 2012 1:16:50 PM UTC-5, David Pilato wrote: > Yes. That's this field. Sounds like you are using a BigCouch instance, > don't you? If so, you handle right now more than 100 millions changes, > right? > > In that case, you have to find the right change id given by bigcouch. I > think it's something like: xxxxxxx-BIGCOUCHADDON, where xxxxxxx is the real > seq number in couchDb. > > David. > > Le 18 décembre 2012 à 19:09, JP Toto \<[james....@gmail.com](mailto:james....@gmail.com) \\> > a écrit : > > David, > > Thanks for the reply! Do you mean the the last\_seq field? Right now that > looks like the below: If I set it to a previous id, will it dupe any > documents that are after that? I don't mind overwriting documents but I > don't want to duplicate any. > > Thanks for the help! > > - last\_seq: > 109019340-g1AAAAXpeJyV1DssQ1EYB\_AbxGCXGCQGm0TjuUk0kXq03nxEDdKvtwlVvVLtym4zGMT7zdktFpsEs1liY\_N-FMf\_u1un5rvLf7m\_\_3nce07KcZyq6VLXqXU57mUSQZebA\_PeQnYulpltaGgMxFNezo2ls4F0IpvCyyUxhyuMOU2yE5qoU0lxhiuJRgT3Xukw3CjXWPsruL-mEDcVwXB\_XGfMseDucd3IcCfcSjQkOPijw3DD3G5tXnCUdRjuh8PGHAoevSzEjUUw3BET0YC\_29W6keEGecraL3\_kvA7DfXPSmH3Bg8rvDHfAOaI-weEb3Zrh-nnJ2g\_BkR3dyHCf6TJn15hlf-L1Kg65B4mIEK1KgRfVFvRCIt6s3ZaCtvvCgpaiBe-QiG0cNCkYftDOYAcS0UN0JgV9x9qCMCTixdoL\_6CeawteIRGbxlxLQceKdg-2IBFdRLdSMKS7pCC7IRFP1t75S1jUFjxDItaNefT\_w3JtwQYkIkT0JgVja6rbDrITEmHxSMHkTPIfOl4Kww > > } > > On Tuesday, December 18, 2012 12:59:13 PM UTC-5, David Pilato wrote: > > What you can probably do is to modify the meta data of the river. As far > as I remember, you will find the latest change number that Elasticsearch > process. > You can update this particular document and set the field to xxxx (1 if > you want to start from the begining). > > Does it help? > > David. > > Le 18 décembre 2012 à 18:56, JP Toto \< [james....@gmail.com](mailto:james....@gmail.com)\> a écrit : > > Hi all! > > Having an issue similar to > [Redirecting to Google Groups](https://groups.google.com/forum/?fromgroups=#!searchin/elasticsearch/river$20missing/elasticsearch/Y8G4eu-sbrE/bNyopwUP_kgJ) > > We had a node failure which we repaired and brought back up. ES re > balanced itself and is all green (using 0.19.2). We're using the CouchDB > river which generally works well. However, it missed some documents while > we were down and now we have a gap that it doesn't' seem to be filling in. > > Is there a way to have the \_river re-scan \_changes or bootstrap it > somehow? We're not sure how to get the gaps filled in. > > Thanks! > > -- > > [https://groups.google.com/forum/?fromgroups=#!searchin/elasticsearch/river$20missing/elasticsearch/Y8G4eu-sbrE/bNyopwUP\_kgJ](https://groups.google.com/forum/?fromgroups=#!searchin/elasticsearch/river$20missing/elasticsearch/Y8G4eu-sbrE/bNyopwUP_kgJ) > > -- > David Pilato > > [https://groups.google.com/forum/?fromgroups=#!searchin/elasticsearch/river$20missing/elasticsearch/Y8G4eu-sbrE/bNyopwUP\_kgJ](https://groups.google.com/forum/?fromgroups=#!searchin/elasticsearch/river$20missing/elasticsearch/Y8G4eu-sbrE/bNyopwUP_kgJ) > [http://www.scrutmydocs.org/](http://www.scrutmydocs.org/) > [http://dev.david.pilato.fr/](http://dev.david.pilato.fr/) > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > -- > > -- > David Pilato > [http://www.scrutmydocs.org/](http://www.scrutmydocs.org/) > [http://dev.david.pilato.fr/](http://dev.david.pilato.fr/) > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs -- ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [December 18, 2012, 6:45pm UTC](https://discuss.elastic.co/t/couchdb--river-es-failure-and-missing-docs/10109/7 "2012-12-18T18:45:40Z")
I think it will update the docs in elasticsearch because documents have the same \_id in bigcouch and elasticsearch. You can check that by getting an id in BigCouch and do curl localhost:9200/index/type/YOURBIGCOUCHID and see if you can retrieve the document from elasticsearch. I'm almost sure it will work. Le 18 décembre 2012 à 19:21, JP Toto [james.p.toto@gmail.com](mailto:james.p.toto@gmail.com) a écrit : > Resetting the id won't dupe the subsequent docs in ES right? > > On Tuesday, December 18, 2012 1:16:50 PM UTC-5, David Pilato wrote: > > > > Yes. That's this field. Sounds like you are using a BigCouch > > > instance, don't you? If so, you handle right now more than 100 millions > > > changes, right? > > > > In that case, you have to find the right change id given by bigcouch. I > > think it's something like: xxxxxxx-BIGCOUCHADDON, where xxxxxxx is the real > > seq number in couchDb. > > > > David. > > > > Le 18 décembre 2012 à 19:09, JP Toto \< [james....@gmail.com](mailto:james....@gmail.com)\> a écrit : > > > > ``` > > > > > David, > > > > ``` > > > > > ``` > > > Thanks for the reply! Do you mean the the last_seq field? Right now > > > > > > ``` > > > > > > that looks like the below: If I set it to a previous id, will it dupe any > > > documents that are after that? I don't mind overwriting documents but I > > > don't want to duplicate any. > > > > > > ``` > > > Thanks for the help! > > > > > > * last_seq: > > > > > > ``` > > > > > > 109019340-g1AAAAXpeJyV1DssQ1EYB\_AbxGCXGCQGm0TjuUk0kXq03nxEDdKvtwlVvVLtym4zGMT7zdktFpsEs1liY\_N-FMf\_u1un5rvLf7m\_\_3nce07KcZyq6VLXqXU57mUSQZebA\_PeQnYulpltaGgMxFNezo2ls4F0IpvCyyUxhyuMOU2yE5qoU0lxhiuJRgT3Xukw3CjXWPsruL-mEDcVwXB\_XGfMseDucd3IcCfcSjQkOPijw3DD3G5tXnCUdRjuh8PGHAoevSzEjUUw3BET0YC\_29W6keEGecraL3\_kvA7DfXPSmH3Bg8rvDHfAOaI-weEb3Zrh-nnJ2g\_BkR3dyHCf6TJn15hlf-L1Kg65B4mIEK1KgRfVFvRCIt6s3ZaCtvvCgpaiBe-QiG0cNCkYftDOYAcS0UN0JgV9x9qCMCTixdoL\_6CeawteIRGbxlxLQceKdg-2IBFdRLdSMKS7pCC7IRFP1t75S1jUFjxDItaNefT\_w3JtwQYkIkT0JgVja6rbDrITEmHxSMHkTPIfOl4Kww > > > } > > > > > > ``` > > > On Tuesday, December 18, 2012 12:59:13 PM UTC-5, David Pilato > > > > > > ``` > > > > > > wrote: > > > \> \> \> \> What you can probably do is to modify > > > \> \> \> \> the meta data of the river. As far as I remember, > > > \> \> \> \> you will find the latest change number that > > > \> \> \> \> Elasticsearch process. > > > > > > > ``` > > > > You can update this particular document and set the field > > > > > > > > ``` > > > > > > > > to xxxx (1 if you want to start from the begining). > > > > > > > > ``` > > > > Does it help? > > > > > > > > David. > > > > > > > > Le 18 décembre 2012 à 18:56, JP Toto < > > > > > > > > ``` > > > > > > > > [james....@gmail.com](mailto:james....@gmail.com)\> a écrit : > > > > > > > > ``` > > > > > > > > > Hi all! > > > > > > > > ``` > > > > > > > > > ``` > > > > > Having an issue similar to > > > > > > > > > > ``` > > > > > > > > > > [Redirecting to Google Groups](https://groups.google.com/forum/?fromgroups=#!searchin/elasticsearch/river$20missing/elasticsearch/Y8G4eu-sbrE/bNyopwUP_kgJ) > > > > > [https://groups.google.com/forum/?fromgroups=#!searchin/elasticsearch/river$20missing/elasticsearch/Y8G4eu-sbrE/bNyopwUP\_kgJ](https://groups.google.com/forum/?fromgroups=#!searchin/elasticsearch/river$20missing/elasticsearch/Y8G4eu-sbrE/bNyopwUP_kgJ) > > > > > > > > > > ``` > > > > > We had a node failure which we repaired and brought > > > > > > > > > > ``` > > > > > > > > > > back up. ES re balanced itself and is all green (using 0.19.2). We're > > > > > using the CouchDB river which generally works well. However, it missed > > > > > some documents while we were down and now we have a gap that it > > > > > doesn't' seem to be filling in. > > > > > > > > > > ``` > > > > > Is there a way to have the _river re-scan _changes or > > > > > > > > > > ``` > > > > > > > > > > bootstrap it somehow? We're not sure how to get the gaps filled in. > > > > > > > > > > ``` > > > > > Thanks! > > > > > > > > > > -- > > > > > > > > > > > > > > > > > > > > -- > > > > > David Pilato > > > > > > > > > > > > > > > http://www.scrutmydocs.org/ > > > > > > > > > > ``` > > > > > > > > > > [http://www.scrutmydocs.org/](http://www.scrutmydocs.org/) > > > > > [http://dev.david.pilato.fr/](http://dev.david.pilato.fr/) > > > > > [http://dev.david.pilato.fr/](http://dev.david.pilato.fr/) > > > > > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > > > > > > > > > ``` > > > > > -- > > > > > > > > > > > > > > > > > > > > > > > > ``` > > > > > > > > > > > > > > > > > > ``` > > > -- > > > David Pilato > > > http://www.scrutmydocs.org/ > > > http://dev.david.pilato.fr/ > > > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > > > > > ``` > > > > > > > > > > > > -- > > > > > -- David Pilato [http://www.scrutmydocs.org/](http://www.scrutmydocs.org/) [http://dev.david.pilato.fr/](http://dev.david.pilato.fr/) Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs -- ---
**Author:** ![JP\_Toto](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jp_toto/32/2512_2.png) [@JP\_Toto](https://discuss.elastic.co/u/JP_Toto)\ **Post date:** [December 18, 2012, 9:52pm UTC](https://discuss.elastic.co/t/couchdb--river-es-failure-and-missing-docs/10109/8 "2012-12-18T21:52:33Z")
Thanks, David I really appreciate the suggestion. We're just trying to figure out how to match update\_seq to a document to figure out where to start from. On Tuesday, December 18, 2012 1:45:40 PM UTC-5, David Pilato wrote: > I think it will update the docs in elasticsearch because documents have > the same \_id in bigcouch and elasticsearch. > > You can check that by getting an id in BigCouch and do > curl localhost:9200/index/type/YOURBIGCOUCHID and see if you can retrieve > the document from elasticsearch. > > I'm almost sure it will work. > > Le 18 décembre 2012 à 19:21, JP Toto \<[james....@gmail.com](mailto:james....@gmail.com) \\> > a écrit : > > Resetting the id won't dupe the subsequent docs in ES right? > > On Tuesday, December 18, 2012 1:16:50 PM UTC-5, David Pilato wrote: > > Yes. That's this field. Sounds like you are using a BigCouch instance, > don't you? If so, you handle right now more than 100 millions changes, > right? > > In that case, you have to find the right change id given by bigcouch. I > think it's something like: xxxxxxx-BIGCOUCHADDON, where xxxxxxx is the real > seq number in couchDb. > > David. > > Le 18 décembre 2012 à 19:09, JP Toto \< [james....@gmail.com](mailto:james....@gmail.com)\> a écrit : > > David, > > Thanks for the reply! Do you mean the the last\_seq field? Right now that > looks like the below: If I set it to a previous id, will it dupe any > documents that are after that? I don't mind overwriting documents but I > don't want to duplicate any. > > Thanks for the help! > > - last\_seq: 109019340-g1AAAAXpeJyV1DssQ1EYB\_AbxGCXGCQGm0TjuUk0kXq03nxEDdKvtwlVvVLtym4zGMT7zdktFpsEs1liY\_N-FMf\_u1un5rvLf7m\_\_3nce07KcZyq6VLXqXU57mUSQZebA\_PeQnYulpltaGgMxFNezo2ls4F0IpvCyyUxhyuMOU2yE5qoU0lxhiuJRgT3Xukw3CjXWPsruL-mEDcVwXB\_XGfMseDucd3IcCfcSjQkOPijw3DD3G5tXnCUdRjuh8PGHAoevSzEjUUw3BET0YC\_29W6keEGecraL3\_kvA7DfXPSmH3Bg8rvDHfAOaI-weEb3Zrh-nnJ2g\_BkR3dyHCf6TJn15hlf-L1Kg65B4mIEK1KgRfVFvRCIt6s3ZaCtvvCgpaiBe-QiG0cNCkYftDOYAcS0UN0JgV9x9qCMCTixdoL\_6CeawteIRGbxlxLQceKdg-2IBFdRLdSMKS7pCC7IRFP1t75S1jUFjxDItaNefT\_w3JtwQYkIkT0JgVja6rbDrITEmHxSMHkTPIfOl4Kww > } > > On Tuesday, December 18, 2012 12:59:13 PM UTC-5, David Pilato wrote: > > ``` > What you can probably do is to modify the meta data of the river. As > > ``` > > far as I remember, you will find the latest change number that > Elasticsearch process. > You can update this particular document and set the field to xxxx (1 > if you want to start from the begining). > > ``` > Does it help? > > ``` > > David. > > Le 18 décembre 2012 à 18:56, JP Toto \< [james....@gmail.com](mailto:james....@gmail.com)\> a écrit : > > Hi all! > > ``` > Having an issue similar to > > ``` > > [Redirecting to Google Groups](https://groups.google.com/forum/?fromgroups=#!searchin/elasticsearch/river$20missing/elasticsearch/Y8G4eu-sbrE/bNyopwUP_kgJ) > > ``` > We had a node failure which we repaired and brought back up. ES re > > ``` > > balanced itself and is all green (using 0.19.2). We're using the CouchDB > river which generally works well. However, it missed some documents while > we were down and now we have a gap that it doesn't' seem to be filling in. > > ``` > Is there a way to have the _river re-scan _changes or bootstrap it > > ``` > > somehow? We're not sure how to get the gaps filled in. > > ``` > Thanks! > > ``` > > -- > > [https://groups.google.com/forum/?fromgroups=#!searchin/elasticsearch/river$20missing/elasticsearch/Y8G4eu-sbrE/bNyopwUP\_kgJ](https://groups.google.com/forum/?fromgroups=#!searchin/elasticsearch/river$20missing/elasticsearch/Y8G4eu-sbrE/bNyopwUP_kgJ) > > -- > David Pilato > > [https://groups.google.com/forum/?fromgroups=#!searchin/elasticsearch/river$20missing/elasticsearch/Y8G4eu-sbrE/bNyopwUP\_kgJ](https://groups.google.com/forum/?fromgroups=#!searchin/elasticsearch/river$20missing/elasticsearch/Y8G4eu-sbrE/bNyopwUP_kgJ) > [http://www.scrutmydocs.org/](http://www.scrutmydocs.org/) > [http://dev.david.pilato.fr/](http://dev.david.pilato.fr/) > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > -- > > -- > David Pilato > [http://www.scrutmydocs.org/](http://www.scrutmydocs.org/) > [http://dev.david.pilato.fr/](http://dev.david.pilato.fr/) > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs > > -- > > -- > David Pilato > [http://www.scrutmydocs.org/](http://www.scrutmydocs.org/) > [http://dev.david.pilato.fr/](http://dev.david.pilato.fr/) > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs -- ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:59am UTC](https://discuss.elastic.co/t/couchdb--river-es-failure-and-missing-docs/10109/9 "2017-07-06T02:59:25Z")