nextcloud / nextcloud/serverinfo
Replica lag reported, although no replica configured
Open
Nobody has claimed this yet.
0. Needs triage
bug
- Dominant language
- JavaScript
- Stars
- 130
- Forks
- 64
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 49
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Steps to reproduce
- Install dbdoctor
- Check the alerts
Expected behaviour
No alert about replication (since there's no replication)
Actual behaviour
Server configuration
Database: 12.0.2-MariaDB-deb13
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by installing dbdoctor and checking the alerts with the reported MariaDB 12.0.2 configuration. Trace how replication alerts are generated when no replica is configured, then verify that the alert is absent in that setup while genuine replication alerts remain detectable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, mariadb
- Domain
- databases, observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100