Timeline for Why was my ceph specific question marked as a duplicate of a generalized question by multiple users?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 11, 2018 at 15:03 | comment | added | Sven Mod | We don't accept capacity planning questions. If your question is "I have resource X - is this enough to do Y" or "How much of X do I need to do Y" then it's not welcome here. The reason is is that in 99% of cases there is no simple rule and you have to test for your specific workload. It might be that this isn't true for Ceph and there is an easy formula to follow, but even then I guess it's just a rule of thumb and the full answer is more complex with a lot of "it depends". | |
| Aug 11, 2018 at 14:41 | comment | added | Cheyenne Forbes | in the description I have "The case is 28TB", I'm still lost to how is the question a duplicate | |
| Aug 8, 2018 at 0:23 | comment | added | Cheyenne Forbes | "1GB RAM per TB storage recommendation still stands as far as I know plus you want some for the OS and some safety margin so in your case 64GB seem sensible" is what I got from the ceph community, the answer I was looking for. | |
| Aug 7, 2018 at 19:54 | comment | added | Cheyenne Forbes | take me asking a SeaweedFS specific question for example, someone who has it in production made server recommendations based on the fact that we have the same use case github.com/chrislusf/seaweedfs/issues/425 I was expecting the same here, someone actually made a valid answer relating to using ceph with RC and it made sense | |
| Aug 7, 2018 at 19:46 | history | answered | SvenMod | CC BY-SA 4.0 |