Details
Description
List of issues addressed in the 3.1.4 release
Attachments
Issue Links
- depends on
-
MB-16292 State of vBucket on new master set to "replica" instead of "pending" during DCP takeover
- Resolved
-
MB-17391 Revert change to set state of vbucket to "pending" (instead of replica) on new master during takeover (MB-16292)
- Closed
-
MB-17502 Rebalance performance regressed in 3.1.4
- Closed
-
MB-17787 XDCR Replication regressed in 3.1.4
- Closed
-
MB-17889 View query latency slower in 3.1.4-1836 (compared to 1835).
- Closed
-
MB-16266 Manual actions after Upgrade
- Closed
-
MB-16656 Wrong high sequence number returned from ep-engine
- Closed
-
MB-16752 [Backport 3.1.x] Check that the file handle on the memcached log was open correctly
- Closed
-
MB-17241 Janitor activation of vbucket post rebalance failure results in unnoticed dead DCP stream
- Closed
-
MB-17766 mcd abort during rebalance
- Closed
-
MB-18131 CLONE - [revAB] 80% regression in APPEND operation latency
- Closed
-
MB-16357 A race between compaction thread and the memcached thread that changes the vbucket state could fire an assertion crash
- Closed
-
MB-16632 Reduce lock contention between store operations and DCP
- Closed
-
MB-17006 DCP Producer could miss streaming items from certain streams
- Closed
-
MB-17026 Can't retrieve sequence number
- Closed
-
MB-17279 Explicitly close DCP streams after abrupt rebalance termination
- Closed
-
MB-17628 [system test] Rebalance failed with 'setup_replications_failed'
- Closed
-
MB-18171 ep-engine: circular reference between ActiveStream & ActiveStreamCheckpointProcessorTask causes memory leak.
- Closed
-
MB-17132 Generate new UUID for a node when it is added to a cluster
- Closed
-
MB-17220 Log separate messages for checkpoint persistence and seqno persistence commands
- Closed
-
MB-17168 EP engine should log a message and relevant stats when it changes the state of vBucket to dead
- Closed
- mentioned in
-
Page Loading...