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

Problem with retransmission: message not found

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 2.4.1 SP4, 2.5
    • 2.4.1 SP1
    • None
    • High

    Description

      Sometimes a sender cannot find a message with a seqno as requested by a receiver. The seqno requested (47176) was already purged, sent_msgs: [48059 - 48090] (32)

      This could be either an issue in STABLE, which prematurely purges messages although not all members agreed on the highest seqnos seen, or NAKACK, which might incorrectly 'change' seqnos. Very hard to reproduce !

      Trace:
      42032 [ERROR] [OOB Thread,perf,10.68.32.33:32968] NAKACK.handleXmitReq(): - (requester=10.68.28.33:33763, local_addr=10.68.32.33:32968) message 10.68.32.33:32968::47176 not found in sent msgs [48059 - 48090] (32)

      Attachments

        1. tmp.txt
          4 kB
        2. tmp2.txt
          4 kB
        3. udp-atl.xml
          3 kB

        Issue Links

          is related to

          Task - Represents a small unit of work that is not end-user facing. JGRP-528 NAKACK: spurious retransmission requests

          • 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

          Task - Represents a small unit of work that is not end-user facing. JGRP-281 NAKACK: merge sent_msgs, received_msgs and delivered_msgs into xmit_table

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

          Task - Represents a small unit of work that is not end-user facing. JGRP-528 NAKACK: spurious retransmission requests

          • 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:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: