Azure / Azure/AzureStack-QuickStart-Templates
sql-2016-alwayson - First SQL-Server throwing communication errors
- Dominant language
- PowerShell
- Stars
- 587
- Forks
- 741
- PR merge metrics
- No merged PRs in 30d
Description
Hi there,
we're currently trying to deploy sql-2016-alwayson on our lab-system. The deployment as it is, works pretty well but we're currently facing the issue that one of two SQL-Servers is throwing errors that the aoglistener and the aodns seem to be offline.
The other SQL-server doesn't throw errors and sees the aodns and aoglistener online.
Is it intended to work this way or did we missed out on something?
Best regards
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the sql-2016-alwayson deployment described in the issue and compare the two SQL-Server instances' reported AOG listener and AODNS states. Confirm whether the differing communication errors are expected and identify the missing deployment or configuration detail; the issue provides no file or test to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, sql
- Domain
- cloud, databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100