Uploaded image for project: 'mod_cluster'
  1. mod_cluster
  2. MODCLUSTER-645

Different handling of max-attempts parameter on Undertow and httpd implementation

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Critical
    • None
    • 1.3.5.Final
    • None
    • None
    • Documentation (Ref Guide, User Guide, etc.), User Experience

    Description

      The behavior of balancer is different on httpd in comparsion with Undertow implementation when max-attempts parameter is set.

      • Undertow: max-attempts is total count of requests made by balancer in failover scenario. When max-attemps is set to 1 and target worker fails after first attempt made by balancer, no further attempts are made.
      • httpd: max-attempts is count of retries made by balancer after first attempt fails. When max-attempts is set to 1 and target worker fails after first attempt made by balancer, second worker is chosen and request is sent towards it.

      This doesn't seem right and I suggest to unify behavior across implementations.

      Attachments

        Issue Links

          incorporates

          Bug - A problem which impairs or prevents the functions of the product. UNDERTOW-1315 Undertow mod_cluster balancer retries one less time

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. WFLY-10093 mod_cluster "max-attempts" attribute description is incorrect

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JBEAP-10145 (max-retries/max-attemps) Failover configuration issue

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          relates to

          Bug - A problem which impairs or prevents the functions of the product. UNDERTOW-1042 Disabling failover with max-attemps ignored

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            Public project attachment banner

              context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
              current Project key: MODCLUSTER

              People

                rhn-engineering-rhusar Radoslav Husar
                jkasik@redhat.com Jan Kasik
                Jan Kasik Jan Kasik
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: