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

        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.

          People

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

            Dates

            • Created:
              Updated:

              Development