CouchBase异常。 该文件发生了变异

I have CouchBase server.

And have a question about concurrent document mutations:

Code example with saving data in CouchBase:

try {
  Yii::$app->Couch->set($key, $data, 0, '', 1);

} catch (\Exception $e) {

    $already_saved = Yii::$app->Couch->get($key);

        'CouchBase exception',
            'exception' => $e->getMessage(),
            'key' => $key,
            'need_saved' => $data,
            'already_saved' => $already_saved,
            'equal' => md5($already_saved)==md5(json_encode($data))

 * Store a document in the cluster.
 * The set operation stores a document in the cluster. It differs from
 * add and replace in that it does not care for the presence of
 * the identifier in the cluster.
 * If the $cas field is specified, set will <b>only</b> succeed if the
 * identifier exists in the cluster with the <b>exact</b> same cas value
 * as the one specified in this request.
 * @param string $id the identifier to store the document under
 * @param object|string $document the document to store
 * @param integer $expiry the lifetime of the document (0 == infinite)
 * @param string $cas a cas identifier to restrict the store operation
 * @param integer $persist_to wait until the document is persisted to (at least)
 *                            this many nodes
 * @param integer $replicate_to wait until the document is replicated to (at least)
 *                            this many nodes
 * @return string the cas value of the object if success
 * @throws CouchbaseException if an error occurs
function set($id, $document, $expiry = 0, $cas = "", $persist_to = 0, $replicate_to = 0) {


But less than 0.002% from all messages I receive Exception:

CouchBase exception. The document was mutated.

Find this in documentation:

CAS is an acronym for Compare And Swap, and is known as a form of optimistic locking. The CAS can be supplied by applications to mutation operations ( insert, upsert, replace). When applications provide the CAS, server will check the application-provided version of CAS against its own version of the CAS:

  • If the two CAS values match (they compare successfully), then the mutation operation succeeds.

  • If the two CAS values differ, then the mutation operation fails

But still can't understand, what this mutation means?

  • Why if CAS values match, then the mutation operation succeeds, isn't it just rewrite message data?

  • Why if values differ, then the mutation operation fails?

  • Why I receive this Exception?

doutouhe5343 有谁知道?
4 年多之前 回复
doujie9882 谁能帮我?
4 年多之前 回复


您可以将CAS视为“修订号”,它描述了该文档,但这些“修订号”未被订购,您允许 只是告诉两个修订是否相同。 对于文档的每次更改,服务器都会生成新的CAS值(即使您使用相同的内容重写主体,设置过期时间或锁定密钥)。</ p>

所以你可能会看到 发生文档更改时CAS不匹配错误,但内容仍然相同,我可以根据您从身体计算md5的方式猜测它,没有CAS。</ p>
</ div>



You can think about CAS as "revision number", which describes the document, but these "revision numbers" are not ordered, you allowed only to tell if two revisions are the same or not. For every change of the document the server will generate new CAS value (even if you rewrite the body with the same contents, set expiration time or lock the key).

So you might seen the CAS mismatch errors when document change occurred, but the content still the same, I can guess it from how you calculate md5 from the body, without CAS.

Csdn user default icon