[MB-7613] Docs: Working set cleanup Created: 28/Jan/13 Updated: 04/Feb/13 Resolved: 04/Feb/13 |
|
| Status: | Closed |
| Project: | Couchbase Server |
| Component/s: | documentation |
| Affects Version/s: | 2.0 |
| Fix Version/s: | None |
| Security Level: | Public |
| Type: | Bug | Priority: | Major |
| Reporter: | Perry Krug | Assignee: | Karen Zeller |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-admin-tasks-working-set-mgmt.html
-"then both replica data and data written directly the node from clients will be ejected"...not a complete sentence, and we refer to it as "replica data and active data" or "data in replica vbuckets and active vbuckets" -"Note that when you change either of these settings, you provide a percentage of total RAM for a node such as 60%"...they can be set as EITHER a percentage or an absolute number, and are always stored as an absolute number -"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."...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 -Typo: "writes and item" -Typo: "that the items is frequently used" -Why are there two different sections for configuring ejection settings? 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-water-marks.html -This page: http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-admin-tasks-percentage-ejection.html is very confusing, redundant with the previous page, and also refers confusingly to replica and source nodes as opposed to replica/active vbuckets -Typo on above page: "However, if have the server eject a very large percentage of replica data," |
| Comments |
| Comment by Karen Zeller [ 28/Jan/13 ] |
|
-remove duplicate section -fix typos -rewrite to discuss replica and active data and possible ejection. |
| Comment by Karen Zeller [ 28/Jan/13 ] |
| See fixes |
| Comment by Perry Krug [ 29/Jan/13 ] |
|
Thanks Karen. -I still think it's a very odd layout to have those two "settings" sections be separate and so short...why not combine them since they're very related? -It's also a little confusing to show that the watermarks are set as 3.2GB...they're always expressed in full bytes |
| Comment by Karen Zeller [ 29/Jan/13 ] |
|
Oops, when I reassigned back to you for more info, it blew away my questions:
1) Name the sections you want to have consolidated 2) If it is only two subsections it is bad form to consolidate into one: Bad: 1. Main Section a. subsection alone Better 1. Main a. sub 1 b. sub 2 --OR-- 1. Main with everything let me know what makes better sense to our customers |
| Comment by Perry Krug [ 30/Jan/13 ] |
|
I agree that one subsection seems odd, though it would still kind of work in this situation where you would have:
1. Main descriptive information a. How to change settings But if that's still a problem, I would say putting the whole thing together...it's really awkward IMO to have these very small sections separated if the user is trying to read/understand all that's available. |
| Comment by Karen Zeller [ 31/Jan/13 ] |
|
I'm going to go with the "main section with everything approach" then.
I've added the absolute byte info you have here. |
| Comment by Karen Zeller [ 04/Feb/13 ] |
|
Final fixes, consolidation and cross ref:
https://github.com/couchbase/docs/commit/da01c1a9cb0a1f0552ab0a0cb4009495945df722 |
| Comment by Karen Zeller [ 04/Feb/13 ] |
|
Final fixes, consolidation and cross ref:
https://github.com/couchbase/docs/commit/da01c1a9cb0a1f0552ab0a0cb4009495945df722 |