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. New Feature MXS-3012
    Allow for ranking of servers for failover
  2. New Feature MXS-3357
    Priority of Master Promotion
  3. Bug MXS-2676
    High Ping peaks
  4. Bug MXS-2488
    Master Recovery With Delayed Slaves
  5. New Feature MXS-4737
    Graceful shutdown of MaxScale when using more than one MaxScale instance
  6. New Feature MXS-4705
    Support multiple IPs for one server
  7. New Feature MXS-3136
    replacement for rsync.sh from columnstore
  8. New Feature MXS-3898
    Add a way to define and switch different timeouts for primary and replicate during failover
  9. New Feature MXS-4244
    Parameter to prevent promotion of a replica which has had Error 1236
  10. Bug MXS-2651
    Failover/switchover on empty MariaDB replication cluster fails
  11. New Feature MXS-2604
    Requesting a shared cache betwenn several MaxScale instances
  12. Bug MXS-3752
    Automatic rejoin failed
  13. Bug MXS-1937
    Failover/switchover does not disable/enable server events
  14. New Feature MXS-1984
    Allow the source command in the new promotion_sql_file option
  15. Bug MXS-2459
    Replication error: 1236 after startup Master Slave with Maxscale monitor
  16. Bug MXS-2325
    Disabled events are enabled on promoted slave upon failover
  17. New Feature MXS-1687
    Kafka integration failover
  18. New Feature MXS-1686
    Direct Kafka Integration
  19. New Feature MXS-1685
    Automatic Schema Generation
  20. Bug MXS-1681
    Writes are split between failover master and original master on recovery
  21. Bug MXS-1679
    Maxscale does not detect failover executed by another Maxscale in 2 Maxscales + keepalived configuration
  22. Bug MXS-2110
    swithover fails with error Unknown error'. Query: 'FLUSH LOGS
  23. Bug MXS-2016
    Alternate Maxscale Instance hung during failover , CPU usage 500%
  24. Task MXS-1862
    Failover does not happen with Maxscale in Master->Slave replication setup
  25. Task MXS-1857
    Maxscale configuration needed for master<->master replication
  26. New Feature MXS-5991
    Monitor: option to failover to node(s) in the same datacenter
  27. Bug MXS-2371
    Maxscale crashed after losing connection to master database
  28. Bug MXS-3523
    How to change the switching logic of the master?
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