Thank you Jeremy, Would you please share some link where we can find a procedure to do a rolling restart? BR, Sandra
On Tuesday, June 30, 2015 at 11:26:04 AM UTC-5, Jeremy Kelley wrote: > > We were having similar issues with a similar architecture. I cron'd sync > gateway to do a rolling restart throughout the day and it seems to have > "fixed" the issue. -j > > On Tue, Jun 30, 2015 at 11:19 AM Sandra <[email protected] <javascript:>> > wrote: > >> Hello, we are still facing this issue and we haven´t found any way to fix >> it. >> The documents where we see the discrepancies between bucket and it´s >> shadow are being updated (from the mobile app via sync gateway), frequently >> during the day. These documents represent tables in a restaurant and we >> constantly update their status (free, occupied, checking out, etc). >> At the end of the restaurant operation, all the tables are free, and this >> status is correctly stored in the original bucket but not being replicated >> to the shadow bucket, there still appear some tables in another status >> rather than free. >> Seems like it is a issue in couchbase not being able to synchronize >> correctly the original bucket and its shadow bucket when a document changes >> frequently. >> I know that this issue seems weird, but we do see it very commonly and we >> would really appreciate any clue to help us fix it. >> Thank you, Sandra >> >> >> On Thursday, May 7, 2015 at 1:11:46 PM UTC-5, Sandra Bazan wrote: >>> >>> Hello, >>> We are developing an application that has two parts: a Web Side and a >>> mobile side. Operative part is done in the mobile side and Web side is used >>> mainly for configuration and reporting. >>> We are noticing discrepancies between the data that is shown in >>> mobile side (which is connected to couches server via sync gateway) vs web >>> reports which read the info via N1QL from shadow bucket. >>> We have some questions: >>> 1) How can we ensure consistency between the original bucket and the >>> shadow bucket? >>> 2) How close is the time when N1QL will be able to read only current >>> versions instead of retrieving all document revisions?The only reason why >>> we are using shadow bucket is because we've been not able to make N1QL >>> retrieve document current version only, it retrieves all document versions. >>> >>> We appreciate your help, >>> Best regards, >>> Sandra >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Couchbase Mobile" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/mobile-couchbase/781b663d-f22e-4bd3-99c8-91181fc698ee%40googlegroups.com >> >> <https://groups.google.com/d/msgid/mobile-couchbase/781b663d-f22e-4bd3-99c8-91181fc698ee%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/96c06a56-5056-4928-9e13-8fc84c721218%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
