Uploaded image for project: 'JGroups'
  1. JGroups
  2. JGRP-1052

Ergonomics

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 4.0
    • None
    • None
    • 0
    • 0% 0%

    Description

      The goal is to (a) reduce the number of properties needed and (b) determine the values dynamically.

      Examples:

      • Determine the best min/max size of a thread pool
      • Find out what the best timeout values are for retransmission, e.g. based on average retransmission times
      • Determine the optimal number of credits in FC

      This is similar to the JVM setting where, starting with 1.5, the initial values can be set, but over time, the JVM dynamically changes them.

      In the best case, a config contains only a list of protocols without any properties, and JGroups will figure out the correct values.

      Attachments

        Issue Links

          is related to

          Feature Request - Feature requests from customers and/or users JGRP-1037 Ergonomics: size thread pools dynamically

          • 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

          Feature Request - Feature requests from customers and/or users JGRP-1118 NAKACK: use_mcast_xmit should be set based on the available transport

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Feature Request - Feature requests from customers and/or users JGRP-1053 UNICAST: set retransmission timeout based on actual retransmission times

          • 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.
          • Open

          Feature Request - Feature requests from customers and/or users JGRP-1054 NAKACK: retransmission timeouts based on actual retransmission values

          • 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.
          • Open
          relates to

          Feature Request - Feature requests from customers and/or users JGRP-1129 Ergonomics: size max_bundle_size and max_bundle_timeout (in TP) dynamically

          • 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

          Feature Request - Feature requests from customers and/or users JGRP-1238 STABLE: determine best value for max_bytes

          • 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

          Feature Request - Feature requests from customers and/or users JGRP-1244 Discovery: set max_rank dynamically

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Activity

            People

              rhn-engineering-bban Bela Ban
              rhn-engineering-bban Bela Ban
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: