After removal of conflict documents this issue got resolved. If this comes again then only I can provide client logs. The sync gateway only had this much log, apart from this there were logs of get only.
Just for your information we are using Views on couchbase side, And we had faced issues like that document is not in data service but the key is still present in channel view. In this case the document will not be present.
Please find attached logs in zip file. Whats happening is it connects then EOF exception comes at sync gateway and connection gets closed. then retry happens again.
As a rule of thumb, if one side of the connection fails with an unexpected EOF, then the problem is some kind of fatal error on the other side that caused it to drop the connection immediately. Often this is a crash / panic or unexpected exception. So the log with the EOF error is usually not interesting; it’s the other side you want to look at.
@pankaj.sharma This looks like a problem that could be better managed via Couchbase Support - if you have an SLA, I’d recommend directing the question there.
From the details provided it’s unclear whether this is an EOF that would be expected to be seen if the connection between Sync Gateway and the client was dropped mid-replication, or an EOF being encountered for an otherwise healthy connection.