Rebalance fails with time_out or not_my_vbucket error when continuing a stopped or failed rebalance.
Continuing a stopped or a failed rebalance takes longer time because dispatcher gives more priority to vbucket deletion even though disk write queue has more than 1M items
Issues: MB-4363
membase might stop persisting closed checkpoints to disk after rebalancing in more than one node due to race condition in ep-engine
Issues: MB-4344
Unable to change the admin(REST) port from 8091
Issues: MB-4160
Windows upgrade failed from 1.6.0 to 1.7.0
Workaround: Workaround is to follow upgrade instructions from 1.6.0 to 1.6.5 and then 1.6.5 to 1.7.0
Issues: MB-3932
rpm -U doesn't restore data files after upgrade to 1.7.0
Workaround: Need to re-create a symlink as per the 1.7.0 upgrade instructions
Issues: MB-3922
Membase fails to run on Windows system with PGP (http://www.pgp.com) installed
Workaround: Uninstall PGP on any systems running Membase
Issues: MB-3688
TAP doesn't handle "garbage" data/messages over a dump connection
Issues: MB-3669
Unsynchronized clocks can lead to UI not displaying graphs
Workaround: Make sure all the clocks (and their timezones) are synchronized in a Membase cluster. Best to use NTP or some other synchronization technology
Issues: MB-2833
Can't edit size of Memcached bucket type
Issues: MB-2343
Linux installer tries to start (and fails) "membase-server"
Workaround: Another benign warning
Issues: MB-3797
Memcached process is not shutdown quickly with a high disk write queue
Workaround: Make sure your disk write queue is as low as possible (or 0) before shutting down the service
Issues: MB-3628
Windows upgrade failed from 1.6.0 to 1.7.0
Workaround: Workaround is to follow upgrade instructions from 1.6.0 to 1.6.5 and then 1.6.5 to 1.7.0
Issues: MB-3932
Multi-get can return multiple values during rebalance
Issues: MB-2220
Need better error reporting when trying to run binary as root.
Workaround: Do not run as the root user. Note that this is not the same as installing, which needs to be done by root.
Issues: MB-1475
Known issues when Membase runs out of disk space
Workaround: Monitor your system resources closely and ensure that the Membase nodes don't run out of disk space
Issues: MB-3158
MB-3333 MBS Network Filesystems (CIFS/NFS) are not supported for data file storage. Block-based storage (iSCSI,EBS, etc) should be fine
Issues: MB-3333
mbrestore sometimes shows benign python interrupt error.
Workaround: This should only happen at the very end of the restore and does not affect the data being inserted
Issues: MB-3804
Ubuntu 8.x is unsupported
Issues: MB-2506
With some legacy SDK libraries that use the memcached protocol
only, the test suites provided with the source code may invoke
the flush against the cluster on port 11211
or 11210. If the production cluster has a non-secure bucket
"default" without a password it will flush the entire data from
memory to disk.
This can eventually lead to data loss if there is not a backup from which to restore the flushed data.
Issues: MB-5386
memory utilization is not accounted for correctly in certain situations
Workaround: Workaround is to set the memory quota (either bucket or server level) lower than normal to prevent any swap usage
Can't add 1.7.0 node to 1.6.x cluster
Workaround: Rolling upgrades are not currently supported from 1.6.x to 1.7.0. Use the in-place upgrade instructions.
Issues: MB-3924
Upgrade path 1.6.5.4 to 1.7.0 to 1.7.1 not supported.
Issues: MB-4295
UDP access blocked by malformed request
Issues: MC-158
Amazon "micro" and "small" instances are not supported
Workaround: It is a best practice to use at least "large" instances to provide enough RAM for Membase to run
Issues: MB-3911
Large changes in wall-clock time negatively affect disk persistence ability and GUI display
Workaround: Use NTP to keep systems synchronized and start Membase service after such synchronization has taken place
TAP stats sometimes show up as negative
Issues: MB-3901
'ejectNode' is possibly dangerous to active servers
Workaround: Only use 'ejectNode' on nodes not currently responsible for any vbuckets
Issues: MB-3423