Scribd Logo
Upload

Welcome to Scribd!

  • Conclusion: Suggestion:-Load Balance The Traffic

    Uploaded by

    ANURAG RAJAK
    19 views2 pages
    The document provides a root cause analysis and solution for an issue where transaction manager responses were not being sent for delivery reports, causing records to enter a retry state. Key points: - Records were backing up in the retry queue due to lack of responses from the transaction manager for delivery reports. - This caused backpressure in the message broker and acknowledgment graph. - To resolve it, the queues need to be drained to clear the backlog and traffic should be load balanced going forward to prevent recurrences.

    Original Description:

    root cause data2

    Original Title

    root cause data2

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document provides a root cause analysis and solution for an issue where transaction manager responses were not being sent for delivery reports, causing records to enter a retry state. Key points: - Records were backing up in the retry queue due to lack of responses from the transaction manager for delivery reports. - This caused backpressure in the message broker and acknowledgment graph. - To resolve it, the queues need to be drained to clear the backlog and traffic should be load balanced going forward to prevent recurrences.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    19 views2 pages

    Conclusion: Suggestion:-Load Balance The Traffic

    Uploaded by

    ANURAG RAJAK
    The document provides a root cause analysis and solution for an issue where transaction manager responses were not being sent for delivery reports, causing records to enter a retry state. Key points: - Records were backing up in the retry queue due to lack of responses from the transaction manager for delivery reports. - This caused backpressure in the message broker and acknowledgment graph. - To resolve it, the queues need to be drained to clear the backlog and traffic should be load balanced going forward to prevent recurrences.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 2

    RCA :- INC5213138 

    RCA :- Above issue arise due to TM not sending response for DLR. and records are going
    into retry SV matcher. I have uploaded RCA for same.SV matcher has back pressure due
    to this ack graph has backpressure. some logs are attached with this.

    Conclusion :- We have to do queue drain for this


    Suggestion :- load balance the traffic

    SKV_ACCOUNT_NAME Count(TM_DLR_RESP_SV_NOBIND_RETRY_JMS)
    dg_tata_im3 144945
    dg_tata_im4 852
    SKV_SACL_ST1 27339
    dg_tata_im7 853
    dtech_t8 141
    dg_tata_im6 785
    SKV_Tube_SI12 26851
    SKV_SACL_T7
    dg_swigyc_i1
    SKV_SACL_SI18
    SKV_SACL_SI5 256
    dtech_si7 52694
    SKV_GPSHP_SI13 47802
    dg_bip_imp11 26
    test_2801
    dg_tata_im5 833
    dg_tata_im2 136646
    dg_tata_im1 140834
    SKV_SACL_SI_15 18887
    SKV_VCON_T_2 39
    dg_tata_im8 823
    dg_cdacsit1 46
    Rdg_infi_in33 37671
    dg_tata_im9 840
    dg_bip_imp13 7
    SKV_WTE_SI1 1941
    dg_tata_im10 139667
    SKV_Tube_SI13
    dtech_si8 48
    one_t_dg1 3
    Rdg_infi_in31 82
    test_2800
    dtech_si3 27885
    dtech_si4 78

    2800 port
    SKV_ACCOUNT_NAM Count(TM_DLR_RESP_SV_NOBIND_RETRY_JMS)
    E
    Rcdac_gov1:T 32431
    SKV_SACL_SI23
    dg_bip_tr19
    SKV_SACL_T8
    dtech_t1
    SKV_infis_tr2
    SKV_SACL_SI8
    dtech_t6 32
    dtech_t5
    dg_cdac_t26 11749
    SKV_HALF_SI8 20964
    SKV_DST_T1 124764
    dtech_si1 41
    SKV_DST_T3 11688
    dg_bip_imp14
    dtech_t2 47
    SKV_VCON_T12 2038
    SKV_HALF_SI9 19964
    dtech_si2 10201
    test_2806
    SKV_infis_tr4
    dg_cdac_t25
    test_2816 36
    dg_tata_im5 65005
    Rdg_infi_in31 75397

    2806 port

    You might also like