| Summary | Is there a limitation in Orbix on the number of servers deployed in a domain? |
|---|---|
| Article Number | 15910 |
| Environment | All Supported Operating Systems Orbix 6.3.4 |
| Question/Problem Description | Is there a limitation in Orbix on the number of servers deployed in a domain? Is there a limitation on the size of an Orbix domain? Are there any known problems when scaling up an Orbix domain? |
| Clarifying Information | |
| Error Message | |
| Defect/Enhancement Number | |
| Cause | |
| Resolution | Orbix does not impose any limits on the size of an Orbix domain or on the number of servers deployed in a domain. Theoretically any problems that are likely to be seen when scaling up will most likely be a gradual decrease in performance rather than hitting any limits which will suddenly bring the system to a halt. Any scalability problems boil down to the available underlying hardware and operating system resources. Some operating systems allow limits to be placed on the number of file descriptors a process may open. These kind of limits may affect an Orbix domain, since e.g. each node daemon has a connection to every server it monitors. A node daemon process may run out of file descriptors if a limit has been set for the file descriptors a process can open. Orbix 6 is an incredibly scalable system once it is designed correctly and has been running in complex systems with thousands of CPUs. |
| Workaround | |
| Notes | |
| Attachment |
| Created date: | 06 September 2011 |
|---|---|
| Last Modified: | 13 February 2013 |
| Last Published: | 23 June 2012 |
| First Published date: | 10 September 2011 |
#Orbix
#KnowledgeDocs
