[MB-4512] Incorrect total Cluster Storage , summing up index_path and data_path sizes Created: 07/Dec/11 Updated: 01/Mar/12 Resolved: 01/Mar/12 |
|
| Status: | Closed |
| Project: | Couchbase Server |
| Component/s: | ns_server |
| Affects Version/s: | 2.0-developer-preview-3 |
| Fix Version/s: | 2.0-developer-preview-4, 2.0 |
| Security Level: | Public |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Karan Kumar | Assignee: | Dale Harvey |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | 2.0-DP3-release-notes, 2.0-dev-preview-4-release-notes | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Description |
|
Version: 2.0.0r-266-g480746a
Set the path to /mnt/ebs (100GB size). curl -d path=/mnt/ebs http://localhost:8091/nodes/self/controller/settings 10 node cluster .. Total cluster storage is (1TB (10*100GB)) See the screenshot attached. Here the total size is roughly twice the actual storage available. I think the total storage calculation is doing sum of path and index_path. Here both are same (/mnt/ebs) |
| Comments |
| Comment by Dipti Borkar [ 17/Jan/12 ] |
| Check if this is fixed. Reassigning to QE. |
| Comment by Aleksey Kondratenko [ 17/Jan/12 ] |
| no need. Nobody fixed it yet. |
| Comment by Dale Harvey [ 24/Jan/12 ] |
| It looks easy to fix index_path and data_path being summed when they are mounted on the same disk, however I dont think its going to be possible to determine whether different nodes in the cluster have the same drive mounted (running a 2 node cluster locally I get total storage as 4x my hard drive) |
| Comment by Dale Harvey [ 24/Jan/12 ] |
| http://review.couchbase.org/#change,12655 |
| Comment by Thuan Nguyen [ 25/Jan/12 ] |
|
Integrated in github-ns-server-2-0 #269 (See [http://qa.hq.northscale.net/job/github-ns-server-2-0/269/]) Dont sum index_path and db_path when on the same mount point ( aliaksiej.artamonau : Files : * src/ns_storage_conf.erl |
| Comment by Thuan Nguyen [ 30/Jan/12 ] |
| Verify this bug is fixed on build 2.0.0r-607 on 4 nodes of ubuntu 10.04 64bit. |