Setting a Secondary Throttle Should Not Require Customers to Write to the Config Database

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Cluster Scalability
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Writing directly to the config database should be an item of last resort, customers should not be required to write directly to the config database to set a secondaryThrottle setting

      Customers should be presented a method to create, modify and remove a secondaryThrottle without writing directly to the config server. 

            Assignee:
            Unassigned
            Reporter:
            Matt Panton
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: