Derek Su
Derek Su
@mahdiG Have you checked https://github.com/longhorn/longhorn/issues/7387#issuecomment-1867063797?
cc @mantissahz
cc @PhanLe1010 @shuo-wu @innobead
> > Alternatively, if there's only one running volume experiencing performance degradation, we can either provide users with clear steps to collect the data themselves or integrate benchmark commands directly...
@yangchiu What's the reproduce rate?
@yangchiu In addition, can you check if the issue is reproducible in v1.6.2? Thank you.
> @derekbit is it possibly related to the support of backup failover? or do we support that? cc @ChanYiLin IIRC, we don't support the backup failover. @ChanYiLin Do you know...
Also found a false alarm in the instance-manager pod on `ip-10-0-2-14` ``` 2024-08-03T01:54:08.453947507Z time="2024-08-03T01:54:08Z" level=error msg="Failed to remove old head volume-head-002.img" func="replica.(*Replica).createDisk.func1" file="replica.go:924" error="" ``` Shoud not print error message...
The backuptarget `minio` server is on the rebooted node `10.0.2.198`. After a quick check, I don't see clues related to the stuck backup. The issue should be very rare. @ChanYiLin...
Refine the test case with external backup store cc @longhorn/qa