ActiveMQ
  1. ActiveMQ
  2. AMQ-468

Queue load balancing - optionally give highest priority to the local connection, then local broker then networks

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: NEEDS_REVIEW
    • Component/s: None
    • Labels:
      None

      Description

      For Queues, as an option assign the highest priority for dispatching to the local connection, then the local broker, then the cluster etc.

      Right now we favour consumers on the local broker above consumers on remote brokers. However we should prioritise consumers on the same session, connection or VM transport above consumers in other processes etc

        Activity

        Jeff Turner made changes -
        Project Import Fri Nov 26 22:32:02 EST 2010 [ 1290828722158 ]
        Rob Davies made changes -
        Fix Version/s NEEDS_REVIEWED [ 12186 ]
        Fix Version/s 5.4.0 [ 12110 ]
        Bruce Snyder made changes -
        Fix Version/s AGING_TO_DIE [ 12187 ]
        Fix Version/s 5.4.0 [ 12110 ]
        Bruce Snyder made changes -
        Fix Version/s AGING_TO_DIE [ 12187 ]
        Fix Version/s 5.4.0 [ 12110 ]
        Gary Tully made changes -
        Fix Version/s 5.4.0 [ 12110 ]
        Fix Version/s 5.3.0 [ 11914 ]
        Gary Tully made changes -
        Fix Version/s 5.3.0 [ 11914 ]
        Fix Version/s 5.2.0 [ 11841 ]
        Rob Davies made changes -
        Fix Version/s 5.1.0 [ 11802 ]
        Fix Version/s 5.2.0 [ 11841 ]
        Rob Davies made changes -
        Fix Version/s 5.1.0 [ 11802 ]
        Fix Version/s 5.0.0 [ 11712 ]
        Rob Davies made changes -
        Assignee Rob Davies [ rajdavies ]
        Hiram Chirino made changes -
        Fix Version/s 4.1.0 [ 11691 ]
        Fix Version/s 4.2 [ 11712 ]
        Hide
        james strachan added a comment -

        We mght want to weight consumers via

        • the session (so replies tend to go to the session which sent a message)
        • the connection that sent the message
        • VM connections (which are generally cheaper to use)

        I guess we might want this to be configurable.

        Show
        james strachan added a comment - We mght want to weight consumers via the session (so replies tend to go to the session which sent a message) the connection that sent the message VM connections (which are generally cheaper to use) I guess we might want this to be configurable.
        james strachan made changes -
        Field Original Value New Value
        Description For Queues, as an option assign the highest priority for dispatching to the local connection, then the local broker, then the cluster etc. For Queues, as an option assign the highest priority for dispatching to the local connection, then the local broker, then the cluster etc.

        Right now we favour consumers on the local broker above consumers on remote brokers. However we should prioritise consumers on the same session, connection or VM transport above consumers in other processes etc
        Summary Queue load balancing - optionally give highest priority to the local connection Queue load balancing - optionally give highest priority to the local connection, then local broker then networks
        Rob Davies created issue -

          People

          • Assignee:
            Rob Davies
            Reporter:
            Rob Davies
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development