Menu

#3370 smf: ProcExecLevel is not correct in Balanced In Service Upgrade (BISU)

5.26.02
fixed
None
defect
smf
d
5
minor
False
2026-02-27
2025-04-21
No

The cluster size is 10 (2 SCs and 8 PLs).
The upgrade is configured to run with BISU: numberOfSingleSteps 4.
There are 2 original procedures, the proc0 (ExecLevel 0) will do rolling upgrade SCs and proc1 (ExecLevel 1) will do rolling on PLs.
After BISU configured, there are 4 Balanced procs created corresponding with ExecLevel 2, 3, 8, 9. This is incorrect. Their ExecLevel should be 2, 3, 4, 5.

Related

Wiki: ChangeLog-5.26.02

Discussion

  • Thang Duc Nguyen

    • status: assigned --> review
     
  • Thang Duc Nguyen

    • status: review --> fixed
     
  • Thang Duc Nguyen

    commit 0aea074508136aee5895c3f29d0b22c488c2a86f (HEAD -> develop, origin/develop, ticket-3370)
    Author: thang.d.nguyen thang.d.nguyen@endava.com
    Date: Mon Apr 28 16:44:52 2025 +0700

    smfd: Correct exec level of balanced procedure [#3370]
    
    When the upgrade is configured as balanced in service upgrade (BISU),
    the exec level of balanced proc is set to one higher than the highest
    of the original proc used in balanced groups. The exec level
    of balanced procedures should not be set by another balanced procs.
    
     

Log in to post a comment.

MongoDB Logo MongoDB