How do I choose the correct node roles?

Chris Nelson -

Here are the typical node configurations that are available for your cluster:

All-in-one node, a.k.a. combined node or PACO (proxy-account-container-object) node
  • All services are running on all nodes
  • Most cost-effective for small deployments
  • Maximum redundancy: when one machine fails, all other machines take up the slack
Proxy-storage, a.k.a. proxy and account-container-object
  • Proxy and Storage tiers run on separate nodes 
  • Supports heavy concurrent traffic loads with smaller data sets
  • Dedicated proxy machines handle external HTTP traffic
  • Proxies become a failure scenario; at least two proxy machines are required for redundancy
  • Proxies might be limited by drives on object servers, but this can be solved by increasing the replica count, thereby increasing the total drive count

Proxy, account-container, object

  • Proxy, Account and Container storage, and Object storage tiers all run on separate nodes
  • Supports heavy traffic loads on very large data sets
  • Also supports special scenarios such as very large numbers of small files
  • Modifying objects puts load on the container servers, which can be pulled out into their own tier when they get large enough
  • Cost-effective only for specialized use cases or very large clusters
Have more questions? Submit a request

Comments

Powered by Zendesk