Update the default value of maximum_delay

Bug #1709231 reported by wanghao
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
zaqar
Fix Released
Undecided
wanghao

Bug Description

Now we have decided to update the default value of maximum_delay from 60 to 30 seconds in notification retry policy. That could reduce the unnecessary workload in Zaqar.

wanghao (wanghao749)
Changed in zaqar:
assignee: nobody → wanghao (wanghao749)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to zaqar-specs (master)

Fix proposed to branch: master
Review: https://review.openstack.org/491657

Changed in zaqar:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to zaqar-specs (master)

Reviewed: https://review.openstack.org/491657
Committed: https://git.openstack.org/cgit/openstack/zaqar-specs/commit/?id=db632d7d63c192c82a73cfde70e4e12c40021678
Submitter: Jenkins
Branch: master

commit db632d7d63c192c82a73cfde70e4e12c40021678
Author: wanghao <email address hidden>
Date: Tue Aug 8 11:22:20 2017 +0800

    Update the default value of maximum_delay

    Now we have decided to update the default value
    of maximum_delay from 60 to 30 seconds in
    notification retry policy.

    That could reduce the unnecessary workload in Zaqar.

    Change-Id: I21a2bc9415eb3956c09dfc9d61eadaca8e187d97
    Closes-Bug: #1709231

Changed in zaqar:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.