Views in multi-node Couchbase cluster explained -

I'm new to Couchbase.

I have 2 nodes of Couchbase environment, and I have 20 documents (articles in my application) stored in a bucket. I believe there are 5 articles physically alive in node 1 and others are staying in node 2 because when I close node 1, there are only 15 articles in my application list.

I have been given a 'Order Postdate' list in my application which gives me results from a view like this: ... emit (doc.postdate) ...

Now, for some reason, the list given in my application is always incorrect that some articles are not in the correct position (not according to the date of the post). My only guess is this: There is an index for 5 articles in node 1 and index for node 2 is 15, both of them do their orders correctly in the order index, but after my application (not client) Using the library) get 1 to 15 nodes and get node 2 to 15, this is just a complete list of two lists 20, which is why I saw the wrong order in the article list of my application.

So please tell me my guess is wrong and I have a misconception of the Couchbase server, and I have got any wrong reason for the order list? Any detailed information from the architecture perspective of Couchbase will really be appreciated.

Many thanks in the past.

Be sure to try ascending or descending to see if you are ordering correctly There are criteria for whether it makes any other order (if not, it means that you are not using the scene sequence correctly).

For example

  function (see doctor, meta) {...}   
 see