the two nodes around the joints are made unwalkable too.

THE TWO NODES AROUND THE JOINTS ARE MADE UNWALKABLE TOO. FULL
THE TWO NODES AROUND THE JOINTS ARE MADE UNWALKABLE TOO. CODE

There is no downside if a failure causes both members of a two node cluster to serve up the same static website. So not only are we looking for SPoFs, but we are also looking to balance risks and consequences and the calculus will be different for every deployment However before the system can move services to the surviving node after a failure, in general, it needs to be sure that they are not still active elsewhere. The natural starting point then is to have more than one node. It is impossible to eliminate all risk of downtime and especially when one considers the additional complexity that comes with introducing additional redunancy, concentrating on single (rather than chains of related and therefor decreasingly probable) points of failure is widely accepted as a suitable compromise. The first step towards creating any HA system is to look for and try to eliminate single points of failure, often abbreviated as SPoF.

THE TWO NODES AROUND THE JOINTS ARE MADE UNWALKABLE TOO. FULL

We are continuing to work on making this harder to do, and I actually have a full re-write of the internal way of storing shapes planned (after V1.0) to make this actually impossible, but it’s a huge amount of work.Tl dr - Many people love 2-node clusters because they seem conceptually simpler and 33% cheaper, but while it’s possible to construct good ones, most will have subtle failure modes The reason that breaking and re-joining the shape fixes it is that it shatters it into the smallest possible pieces, then re-assembles them all in the proper order, instead of having the weird / broken / unordered version you started with. Part of the weirdness you’re likely seeing is a result of a shape being represented in a strange way (it’s hard to explain it).

THE TWO NODES AROUND THE JOINTS ARE MADE UNWALKABLE TOO. CODE

The way LightBurn represents shapes internally allows for this, but we’ve made the editing code try really hard not to let these things slip through, and break things up when you disconnect them. It’s possible to make shapes that behave this way, though we’re trying to make it really hard to do this. The inner and outer circles of the O here are obviously not connected, but they’re treated as one object in LightBurn. It’s possible to create a single “shape” that is actually multiple, disconnected shapes, for example, text: The only thing that works is that the break apart function will terminate the connection and then allow auto joining to work, but this is counter intuitive as I have to go through the entire line and reconnect it at every vertex, which takes tons of time.Īny thoughts on this? Seems like a bug to me. What really baffles me, is that when I pull the ends of the lines apart so that they are visibly disconnected, when selecting either line segment lightburn will select both as if they are grouped, but they definately arent. To me, there is no obvious reason why these lines refuse to connect and create a closed shape. When this does not work, a lot of times auto join shapes works or in some cases close path will work, but not this time. In this case, the nodes snap to each other, but refuse to auto join. Usually what works is using node editing to snap the end nodes together. Sometimes I will have a shape made up of seemingly connected lines, but when I use select open shapes, it will show that shape as being open. Hey all, I have been dealing with a recurring issue that I cant seem to figure out.

The two nodes around the joints are made unwalkable too.