[MB-2343] Can't edit size of memcached bucket Created: 29/Sep/10 Updated: 23/Jul/12 Resolved: 19/Jun/12 |
|
| Status: | Resolved |
| Project: | Couchbase Server |
| Component/s: | bucket-engine |
| Affects Version/s: | 1.6.0 beta4 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Matt(old) Ingenthron (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | 1.6.0-release-notes, 1.6.5.3-release-notes, 1.7.0-release-notes, 1.7.1-release-notes | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All
Platform: All |
||
| Flagged: |
Release Note
|
| Description |
|
I've not investigated this fully, but I was experimenting with changing buckets and found that the limit_maxbytes was not changing as I would edit bucket properties.
I would have expected a restart of the bucket and a "flush", but the changes to apply. Note that even after restarting ns_server, I didn't see the changes apply. |
| Comments |
| Comment by Frank Weigel [ 30/Sep/10 ] |
|
Memcached buckets do not need to be able to change size at this point (Right now delete and recreate is your friend...) Is that what you are trying to do? Is it not disabled in the GUI? |
| Comment by Matt(old) Ingenthron (Inactive) [ 01/Oct/10 ] |
|
Memcached bucket size editing is currently *enabled* after creation. It should be disabled (already confirmed with Frank). This should probably also be release noted. If you want to change the size of a memcached bucket, delete it and recreate it. |
| Comment by Perry Krug [ 09/Oct/10 ] |
| Reopening for the purposes of release notes, changing title. |
| Comment by Perry Krug [ 16/Nov/10 ] |
| tagged: releasenotes |
| Comment by Sean Lynch [ 18/Nov/10 ] |
| Assigning to Frank because this requires product requirements. There is currently no way in the default engine (memcached bucket type) to change the size of a bucket without restarting it and losing all your data. |
| Comment by Matt Ingenthron [ 14/Jun/12 ] |
|
Was just asked via email if this is something we want to implement.
I would argue (as I did in |
| Comment by Trond Norbye [ 19/Jun/12 ] |
| We won't fix this now. Reopen the issue when we reevaluate the need for this. |