Derek Su

@seumasdunlop What's your LH version? We recommand you upgrade to v1.3.1. The error is printed but ignored in v1.3.1. I think we can reduce the amount of the error messages.

Yes, v1.3.0 has a [bug](https://github.com/longhorn/longhorn/issues/4160) related this default setting feature. We've fixed in v1.3.1.

For the message ``` time="2022-08-29T07:55:35Z" level=debug msg="CheckEngineImageReadiness: nodes [h1016] don't have the engine image longhornio/longhorn-engine:v1.3.1" ``` It is because the engineimage container is not ready on `h1016` node ``` -...

> I also experienced this problem. In grafana I can see spikes where instance manager takes a lot of cpu cores at random points in time. I should check logs...

After a quick look at the log, just saw lots of replica rebuilding/replenishment and snapshot purge around `2022-09-01T05:39:59`. The system was also busy at `2022-08-31T18:01`. - Some messages in longhorn-manager...

> One of our worker nodes had cpu, disk io and network bandwidth far below capacity but its memory usage was near max capacity. One question Do you know which...

> > One question Do you know which process used up the memory? Your applications or Longhorn's processes? > > I couldn't find which process caused the problem but right...

@mahdiG Can you provide your host infor, e.g. CPU model, ram size, storage configuration? Thank you. This is will be a setting reference in https://github.com/longhorn/longhorn/issues/4516.

Did you expand the volume or restore the etcd?

@shuo-wu Can we add a `--vol-size` in the start engine controller command? Then, the volume size from the volume CR can be the ground truth.