-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replica - Physical Resources Clarity #726
Comments
|
Same physical resources as main refers to CPU and memory. This is most important/necessary to get across, some assumptions created mismatched expectation w/potential customer because they had an assumption that they could "save" on replicas. As to no 2. and 3., in theory it could work, but does depend on the compatibility of architectures so should be tested and we don't actually recommend/guarantee. Tagging @gitbuda to raise flags if I wrote something incorrect. |
@Ana-Marija-design and @gitbuda I need more clarification for "Same physical resources as main refers to CPU and memory.". Does this mean that machines must use two identical CPUs and the same amount of RAM? By identical CPU, I mean the same manufacturer and model. |
The same amount of RAM = hard yes. At the very least, each replica can become a main and will need the same resources to run smoothly. @gitbuda correct me if I've not stated the CPU issue well. |
I've added the callout to the docs. Once we will have some more details we can update the docs one more time. |
Current documentation page for Replication isn't clear enough about the fact that Replicas require the same physical resources as main instances.
@kgolubic feel free to add any potential questions to the issue thread and I'll go on a journey of discovery to find answers for you. (I'll ask Buda:)
Please check and add questions before Tuesday (I got Buda on speed-dial on Tuesdays)
The text was updated successfully, but these errors were encountered: