Details
-
Bug
-
Resolution: Duplicate
-
Minor
-
None
-
3.0
-
Security Level: Public
-
None
-
We use append commands to append short blocks to big values.
We've discovered that during active append phase we have traffic between couchbase nodes TRIPLE in terms of MegaBits/s.
Investigation showed that each small append leads to HUGE TAP_MUTATION event sent over to peer cluster member to store a replica.
Mutation
All mutation events arrive as TAP_MUTATION ( =0x41=) events.
These are conceptualy similar to set commands.We use append commands to append short blocks to big values. We've discovered that during active append phase we have traffic between couchbase nodes TRIPLE in terms of MegaBits/s. Investigation showed that each small append leads to HUGE TAP_MUTATION event sent over to peer cluster member to store a replica. Mutation All mutation events arrive as TAP_MUTATION ( =0x41=) events. These are conceptualy similar to set commands.
-
Untriaged
-
Centos 64-bit
-
Unknown
Description
append commands are effective only client->cluster level.
on cluster.node.active->cluster.node.replica level append mutations are effectively replicated as set commands, and contain huge_old_value+small_appended_value.
that is utterly ineffective.
please consider to optimize this.
Attachments
Issue Links
- duplicates
-
MB-11229 For pre/append operations DCP should only send the append chuck and not the whole document.
-
- Closed
-