Details
-
Feature Request
-
Resolution: Unresolved
-
Major
-
None
-
None
Description
Implement an option for a properly configured slave HC to promote itself to master after acquiring in some controlled manner an exclusive right to act as such.
Analysis (and eventually design) document is at: https://developer.jboss.org/docs/DOC-55491
Attachments
Issue Links
- is blocked by
-
WFCORE-1881 Add isCandidateDomainController() to LocalHostControllerInfo and use it where possible
-
- Open
-
-
WFCORE-1882 Deal with WFCORE-1052 functionality in the HA DC case
-
- Open
-
-
WFCORE-1806 Split DomainModelControllerService into separate services for initializing as a master versus as a slave
-
- Coding In Progress
-
-
WFCORE-1883 Post-boot transition to/from acting as a master or slave HC must be done with management op execution locked out
-
- Coding In Progress
-
-
WFCORE-1940 Propagate a persistent domain config revision number and time stamp around the domain
-
- Coding In Progress
-
-
WFCORE-1879 Master HC should reject registration attempts by slaves that have any management API version greater than its own
-
- Open
-
-
WFCORE-1880 Extension add operation handling should check that the slave HCs are not running later versions of the subsystem management API
-
- Open
-
-
WFCORE-1923 Add configuration option to make the HTTP management interface unavailable on non-master HCs
-
- Open
-
- is related to
-
WFCORE-324 Resolve startup dependency between master hostController and slave hostControllers.
-
- Resolved
-
-
JBEAP-4935 Multiple domain controller for a true HA
-
- Closed
-
-
WFCORE-317 Failed to start server when -backup -cached-dc are used together
-
- Resolved
-
-
WFCORE-316 Slave host does not register to DC when starting with --cached-dc and DC is available
-
- Resolved
-