Menu

#3260 immnd: many clients timeout on the imm api calls

5.21.06
fixed
None
defect
imm
nd
major
False
2021-05-26
2021-05-05
No

In a large cluster (24 nodes), the components have very often been timeout in their imm api calls. This timeout results in a component restart. During single step upgrade, due to the imm timeout, the amf locking nodegroup operation fails because of many component restarts escalated to node failover, etc... This ticket suggests IMMSV_DEFAULT_FEVS_MAX_PENDING and IMMSV_WAIT_TIME to be environment variables so the components can adjust these parameters according to the size of cluster.

Related

Wiki: ChangeLog-5.21.06

Discussion

  • Minh Hon Chau

    Minh Hon Chau - 2021-05-05
    • status: unassigned --> accepted
    • assigned_to: Minh Hon Chau
     
  • Minh Hon Chau

    Minh Hon Chau - 2021-05-17
    • status: accepted --> review
     
  • Minh Hon Chau

    Minh Hon Chau - 2021-05-26
    • status: review --> fixed
     
  • Minh Hon Chau

    Minh Hon Chau - 2021-05-26

    commit eaf187e9a04ee147dacee8d722c09aecf9a52426
    Author: Minh Chau minh.chau@dektech.com.au
    Date: Tue May 18 14:41:59 2021 +1000

    imma: Correctly use IMMA_SYNCR_TIMEOUT [#3260]
    

    commit fa8325e924060496184cb57e43bd7eff3bb71a84
    Author: Minh Chau minh.chau@dektech.com.au
    Date: Tue May 18 14:41:59 2021 +1000

    immnd: Make IMMSV_FEVS_MAX_PENDING environment variable [#3260]
    
     

Log in to post a comment.