Log inSkip to main contentSkip to sidebar
Loading…
Jira
  • Dashboards
  • Projects
  • Issues
  • Give feedback to Atlassian
  • Help
    • Jira Core help
    • Keyboard Shortcuts
    • Issue Reminders help
    • About Jira
    • Jira Credits
  • Log In

Export - CSV (All fields)

Export - CSV (Current fields)

Comma (,) Semicolon (;) Vertical bar (|) Caret (^)

  1. Bug MXS-4282
    Servers that are [Down] may have [Slave of External Server]
  2. Bug MXS-4040
    Mariadbmon constantly logs errors if event scheduler is disabled
  3. Bug MXS-5213
    Erroneous "Cluster gtid domain is unknown" error message during failover
  4. Bug MXS-4834
    MaxScale should log a warning if failover may lose transactions
  5. Task MXS-1636
    M18 Failover presentation
  6. Bug MXS-5008
    Log message on releasing exclusive locks when no lock majority is confusing
  7. Bug MXS-5101
    MariaDB Monitor can kill connections from other monitors during switchover
  8. Task MXS-5098
    Use MASTER_DEMOTE_TO_SLAVE = 1 with MariaDB 10.10 and later
  9. New Feature MXS-5067
    Add "enforce_read_only_servers" feature to MariaDB Monitor
  10. Bug MXS-5407
    Dataloss due to maxscale failover of invalid replica
  11. Task MXS-5587
    Use a multiquery instead of multiple small queries in MariaDB Monitor
  12. Bug MXS-4684
    Detect ALTER EVENT failure on MariaDB 11.0
  13. Bug MXS-4675
    Switchover fails with 'Unknown thread id' error
  14. Task MXS-5538
    Add list-backups command to MariaDB Monitor
  15. Bug MXS-5519
    Documentation regarding mixing of cooperative_monitoring_locks and passive is unclear
  16. Bug MXS-5518
    Documentation of switchover-force lacks warnings
  17. New Feature MXS-5494
    Rebuild-server and related commands should have a progress indicator
  18. Bug MXS-5461
    Tolerate a few connection failures after server has been rebuilt
  19. Bug MXS-3809
    When MariaDBMonitor acquires lock majority, the log message gives the impression that auto_failover is enabled even when it is not configured
  20. Bug MXS-4304
    MariaDB-Monitor spams log with connection errors if server is both [Maintenance] and [Down]
  21. Bug MXS-4295
    Switchover will wait even if slave server are lagging more than switchover_timeout
  22. Task MXS-3017
    Clarify MariaDBMonitor documentation on settings detect_stale_master, detect_standalone_master
  23. Bug MXS-3971
    Failover after switchover fails if no transaction is ran between them
  24. Bug MXS-3966
    MariaDBMonitor does not log connection error on startup
  25. Bug MXS-5165
    MariaDB Monitor rebuild server may try to chown "/var/lib/mysql/" instead of just "/var/lib/mysql"
  26. Bug MXS-3149
    Monitor should remove [Master] when starting swithover
  27. New Feature MXS-3262
    Add create-backup and restore-from-backup commands to MariaDB-Monitor
  28. Task MXS-4398
    Use MASTER_USE_GTID = slave_pos when appropriate
  29. New Feature MXS-2723
    MariaDBMonitor add script event when max_slave_replication_lag is reached
  30. Bug MXS-2880
    Typo in MariaDBMonitor slave connection printing
  31. Task MXS-1944
    Clean up MariaDB Monitor cluster detection and modification
  32. New Feature MXS-1954
    Explain why servers change state
  33. New Feature MXS-1147
    add sticky_master option to MySQL Monitor
  34. Bug MXS-1508
    Failover is sometimes triggered on non-simple topologies
  35. Task MXS-1533
    Try to join standalone servers to a replication cluster.
  36. Task MXS-1768
    Allow switchover with empty new master server
  37. Bug MXS-1747
    Rejoin functions should print better errors
  38. Task MXS-1745
    Save all SlaveStatus rows when querying SHOW ALL SLAVES STATUS
  39. Task MXS-1744
    The Gtid-class should save all triplets
  40. Bug MXS-1272
    MySQL Monitor with a Replication Cluster using MariaDB 5.1 does not report correctly Master details
  41. Task MXS-2384
    Update servers concurrently in MariaDB-Monitor
  42. Bug MXS-2370
    Query timeout warning message does not print reason of timeout
  43. Bug MXS-1680
    Provide clear documentation of Monitor operation
  44. Bug MXS-1672
    STOP SLAVE IO_THREAD causes switchover to wait until timeout
  45. New Feature MXS-1671
    External master support for failover/switchover
  46. Bug MXS-1670
    "alter server abc address=..." does not immediately register in monitor
  47. Bug MXS-2040
    Default monitor timeouts are too short
  48. Bug MXS-735
    MySQL Monitor assigns both Master and Slave status to intermediate master
  49. New Feature MXS-734
    Force Slave Status for nodes in Multi Master Setup
  50. New Feature MXS-136
    Check for MaxScale replication heartbeat table existence before creating
Refresh results
{"errorMessages":["jqlTooComplex"],"errors":{}}
[{"id":-1,"name":"My open issues","jql":"assignee = currentUser() AND resolution = Unresolved order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-2,"name":"Reported by me","jql":"reporter = currentUser() order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-4,"name":"All issues","jql":"order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-5,"name":"Open issues","jql":"resolution = Unresolved order by priority DESC,updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-9,"name":"Done issues","jql":"statusCategory = Done order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-3,"name":"Viewed recently","jql":"issuekey in issueHistory() order by lastViewed DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-6,"name":"Created recently","jql":"created >= -1w order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-7,"name":"Resolved recently","jql":"resolutiondate >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-8,"name":"Updated recently","jql":"updated >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false}]
0.3
0
  • Atlassian Jira Project Management Software
  • About Jira
  • Report a problem

Powered by a free Atlassian Jira open source license for MariaDB Corporation Ab. Try Jira - bug tracking software for your team.

Atlassian