Manuel Bleichner

After a little digging through the code and some more trial and error I found out that the "Unknown Cluster" error message means that the receiver needs to have the...

Thanks a lot for your answer. All our nodes are connected through 10GBit network - so in theory, the network shouldn't be a limiting factor here. I'll try to make...

> Restarting the controller should have cleared the internal cache that prevents a shipment from being aborted. So abort should work now, and after that deleting the snapshots should also...

At the moment, it's still a test setup and right now I'm wiping it to start over with a fresh install.

Next update: I reset my main cluster and tried the L2L scenario again. Manual shipping between clusters via `linstor backup ship` worked like a charm after the remote access issues...

Good to hear. I have given up my experiments for now, though. It seemed to me that Linstor just isn't made for my use case - as soon as a...

Maybe I'm missing something here, but I don't seem to be able to set a negative lower bound on a variable. Is there always an implicit positivity constraint for every...

> I first posted this issue as a comment in #27 because @mbleichner mentioned "inspecting port 3478 with tcpdump, it seems like some (not all) UDP packets use an internal...

Yes, i have observed this behavior in all 1.2.x versions. The manager processes cause a constant (relatively high) baseline cpu usage that seemed to only depend on the number of...

The instance manager pod logs show a lot of polling going on. More than 20 requests per second on average. It looks like this: ``` [longhorn-instance-manager] time="2022-08-02T12:02:23+02:00" level=debug msg="Getting replica...