http://www.couchbase.com/issues This file is an XML representation of an issue en-us 5.2.4 845 26-12-2012 http://www.couchbase.com/issues/browse/MB-7613 Couchbase Server <a href="http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-admin-tasks-working-set-mgmt.html">http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-admin-tasks-working-set-mgmt.html</a> <br/> <br/> -&quot;then both replica data and data written directly the node from clients will be ejected&quot;...not a complete sentence, and we refer to it as &quot;replica data and active data&quot; or &quot;data in replica vbuckets and active vbuckets&quot; <br/> -&quot;Note that when you change either of these settings, you provide a percentage of total RAM for a node such as 60%&quot;...they can be set as EITHER a percentage or an absolute number, and are always stored as an absolute number <br/> -&quot;The pager will try to eject 60% of random replica items from other nodes, and only 40% of items that had been written directly to the node from a client.&quot;...this is very confusing to say that it is ejecting random data from other nodes, and data written directly from a client. Just use the replica vbuckets and active vbuckets concept <br/> -Typo: &quot;writes and item&quot; <br/> -Typo: &quot;that the items is frequently used&quot; <br/> -Why are there two different sections for configuring ejection settings? <a href="http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-admin-tasks-percentage-ejection.html,">http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-admin-tasks-percentage-ejection.html,</a> <a href="http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-admin-tasks-water-marks.html">http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-admin-tasks-water-marks.html</a> <br/> -This page: <a href="http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-admin-tasks-percentage-ejection.html">http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-admin-tasks-percentage-ejection.html</a> is very confusing, redundant with the previous page, and also refers confusingly to replica and source nodes as opposed to replica/active vbuckets <br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-Typo on above page: &quot;However, if have the server eject a very large percentage of replica data,&quot; MB-7613

Docs: Working set cleanup

Bug Major Closed Fixed Public Karen Zeller Perry Krug Mon, 28 Jan 2013 11:56:27 -0600 Mon, 4 Feb 2013 16:46:31 -0600 Mon, 4 Feb 2013 16:46:26 -0600 2.0 documentation 0 1 -remove duplicate section<br/> -fix typos<br/> -rewrite to discuss replica and active data and possible ejection. See fixes Thanks Karen.<br/> <br/> -I still think it&#39;s a very odd layout to have those two &quot;settings&quot; sections be separate and so short...why not combine them since they&#39;re very related?<br/> -It&#39;s also a little confusing to show that the watermarks are set as 3.2GB...they&#39;re always expressed in full bytes<br/> Oops, when I reassigned back to you for more info, it blew away my questions: <br/> <br/> 1) Name the sections you want to have consolidated <br/> <br/> 2) If it is only two subsections it is bad form to consolidate into one: <br/> <br/> Bad: <br/> <br/> &nbsp;&nbsp;&nbsp;&nbsp;1. Main Section <br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;a. subsection alone <br/> <br/> Better <br/> <br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1. Main <br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;a. sub 1 <br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;b. sub 2 <br/> <br/> <br/> --OR-- <br/> <br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1. Main with everything <br/> <br/> <br/> let me know what makes better sense to our customers <br/> <br/> <br/> I agree that one subsection seems odd, though it would still kind of work in this situation where you would have: <br/> 1. Main descriptive information <br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;a. How to change settings <br/> <br/> But if that&#39;s still a problem, I would say putting the whole thing together...it&#39;s really awkward IMO to have these very small sections separated if the user is trying to read/understand all that&#39;s available. I&#39;m going to go with the &quot;main section with everything approach&quot; then. <br/> <br/> I&#39;ve added the absolute byte info you have here. Final fixes, consolidation and cross ref: <br/> <br/> <a href="https://github.com/couchbase/docs/commit/da01c1a9cb0a1f0552ab0a0cb4009495945df722">https://github.com/couchbase/docs/commit/da01c1a9cb0a1f0552ab0a0cb4009495945df722</a> Final fixes, consolidation and cross ref: <br/> <br/> <a href="https://github.com/couchbase/docs/commit/da01c1a9cb0a1f0552ab0a0cb4009495945df722">https://github.com/couchbase/docs/commit/da01c1a9cb0a1f0552ab0a0cb4009495945df722</a> Date of First Response Mon, 28 Jan 2013 14:49:18 -0600 Rank 2973 Sprint Status Time In Status