Azure / Azure/Azure-Data-Factory-Integration-Runtime-in-Windows-Container
Adding second container doesn't work for HA due to order of operations and incorrect remote access command
- Dominant language
- PowerShell
- Stars
- 32
- Forks
- 60
- PR merge metrics
- No merged PRs in 30d
Description
When adding a second container with `ENABLE_HA` and `HA_PORT` specified, the container doesn't correctly get registered and also fails the health check:
I found the following fixes the issue:
1) Use `-EnableRemoteAccessInContainer` instead of `EnableRemoteAccess`
2) Order of operation matters on the Second Node, need to run `-EnableRemoteAccessInContainer` first, before `-RegisterNewNode` is executed
With this setup - the second node is successful:
Enables HA:
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.