They ended maintenance 1 hour earlier, i expected them to you know actually test basic functionality
Printable View
I will admit that I'm more impressed by this mishap than anything else. Things are always going to go wrong in some way, but they did have a full day, so...I guess for SE, that doesn't mean fewer potential problems, it just means they have a full day to mess it up in ways maybe even they didn't know where possible.
Hardware replacement is not a small change. That they only had linkshells break on one DC is a pretty successful implementation for something like this.
This. I'm fine if people don't have infrastructure of software engineering experience but when we who do have that experience say "It's not that simple" then we shouldn't be called white knights for it. It's not that simple, people.
Makes sense. Shorter maintenance is for smaller, quicker changes that are less likely to have unexpected "side effects." Longer maintenance isn't just more time to do the same thing...it means the maintenance itself that is happening is significantly more involved. The more complicated it is, the more likely something goes wrong and needs an extra fix.
Doing a massive hardware transfer is the polar opposite of "very little change." It's a huge undertaking from an IT perspective, and extremely easy for anyone in the field to "defend" it.Quote:
I don't know how they managed this. They had a 24 hour maintenance for what seemed like very little changes, and instead of everything going super smoothly, this happened instead?
I'm seriously trying to be fair. I know there's some people that just want to rip on the game just to rip on it but how do you even defend this?
I'm surprised some people went alil "sparky" with their interpretation of others intellect out of bookshelves. [Eh, ah well, Reddit has a way of screenshotting us now to mock us I saw 20 mins ago]
And this wasn't only just Hardware Replacement and all that entails.
But other things that tie into it, as other Users have stated before. <and I tried to hint before hand without being blunt>
Hence why I'd be curious to know the broadworkings which, like I hinted before, someone that would know, was unlikely to be here at this exact time.
Either way, did things actually get back to normal now.
As some of us have returned from their slumber?
They had a full day to do the implementation but software and the hardware it works with sometimes does unexpected things, and sometimes it's not even something you can catch in testing since it doesn't manifest until all the pieces are chugging along together in a production environment. All said, this is a pretty minor bug for the changes that had to be made. Though I imagine there are probably some more that will come up.