| Summary | Can a slave promotes itself to a Master in a two-node domain in Orbix 6.0? |
|---|---|
| Article Number | 16200 |
| Environment | All Supported Operating Systems Orbix 6.3 |
| Question/Problem Description | Can a slave promotes itself to a Master in a two-node domain in Orbix 6.0? After a master failure, my slave domain refuses to be automatically promoted. Why? |
| Clarifying Information | |
| Error Message | |
| Defect/Enhancement Number | |
| Cause | By default, a slave can not promote itself to a master in a two-node domain. |
| Resolution | In a Orbix 6.3.4 domain, the default configuration does not allow the self promotion of a salve in a two node domain (1 master, 1 slave) if the master go down. Some additional configuration need to occur in order to achieve that. The configuration that need to be changed include "allow_minority_master", "allow_demotion' and "prevent_unilateral_promotion". For more information about these variables and how what values they accept, please see the Orbix Configuration Reference : plugins:pss_db:envs:<env-name>:allow_demotion plugins:pss_db:envs:<env-name>:allow_minority_master plugins:pss_db:envs:<env-name>:prevent_unilateral_promotion |
| Workaround | |
| Notes | Enabling a minority master should be performed with caution. For example, a network partition can cause a slave to be promoted when the master is still running, leading to a duplicate master. Also, after a slave has been promoted, the old master must not be restarted when the new master is not running because updates made after the promotion will be lost. <env-name> should be set to the name of the database that you are interested in promoting. For example it_naming_store for the naming service. |
| Attachment |
| Created date: | 06 September 2011 |
|---|---|
| Last Modified: | 13 February 2013 |
| Last Published: | 23 June 2012 |
| First Published date: | 09 September 2011 |
#KnowledgeDocs
#Orbix
