Tree of Savior Forum

Maintenance = Pool Safety Check?

General Discussion
#1

Ok so I have a serious question here for the computer savy/IT people reading this trainwreck. When these online games take the servers down for 4 or 6 or 8 hours etc how much of that time is actually required for the maintenance and how much of the time is just leftover for the devs to run around by themselves using +100 stage10 trans. Astra Bows to mow down red kepas in the Miner’s Village.

B/c when I read maintenance my mind automatically shifts to the summer, when I take my kids swimming and the fkng lifeguards blow the whistle every 30 minutes to make us get out of the pool. They literally turn their head one way, then look back the other way, taking an entire 15 seconds. At that point they jump in the water and spend the next 14 minutes and 45 seconds tickling and splashing each other in the water in the hopes that they will get some when the pool closes.

1 Like
#2

im in infrastructure support/admin for mnc/conglomerate

in IT, maintenance is just an excuse to bill customer for work we didnt do

incident is one-time job to fix/replace faulty/aging parts.

change ticket is request to upgrade current working design.

tldr, maintenance is just to huehuehue with u IT illiterate

i dont know cars so i bet my mechanics do the same to me with the maintenance

also, big-ass well-structured IT, each are designated to do specific task.
It doesnt matter if u know how to fix server, if your job title is programmer, u dont touch the hardware.
vice versa

but in small IT firm, your the one-guy-for-everything

2 Likes
#3

shutdown, apply patch, coffee break for hours, reboot

1 Like
#4

I always wondered too b/c it seemed like the updates were always just paste/copied from Ktos, we would have always have things leftover in Korean that they missed, dont we still even have a Korean title from like 2 months ago?

#5

IT here for a multinational company

we usually have a 4 hour window for a routinary maintenance of servers

1st and 2nd hour is dedicated to applying patches and perform a reboot
3nd hour is dedicated to remediating any issues
4th hour is dedicated in last checking if services and applications are all up and running

after this, we notify the different teams(sql, application, exchange, etc.) that we have completed our part and its time for them to check on their end if everything is working properly, how long they test im not aware…

5 Likes
#6

extended 2 hours, someone spill coffee on the rack? :slight_smile:

#7

no, steve the janitor/land scaper/coder/lead developer/ceo had to drive to Wendy’s to get a new baked potatoe b/c the premium emotes were too much for the old one to handle

1 Like
#8

‘extended 2 hours’… motherfuckers

#9

There goes my dungeon runs <<
I should’ve known better, but I’m still fighting with my cold and the snow outside that has to be manually removed by me >>

on topic: It would be interesting to know if they do a last code-check before and after applying the patches to find out malicious and unintended interactions which create bugs…
I mean, they managed to bring the same bug to ITOS already twice, so how big is the chance to get it again with each maintenance if they don’t?

Also: How much is the potato?

#10

99 cents, but IMC goes big, Steve gets a chocolate frosty and a jr bacon with cheese, hes fkng loaded from the stupid shi* the whales buy

1 Like
#11

Usually you plan maintenance with a decent buffer, so if something goes wrong, you have time to fix it before users expect the server to be up. On the other side, if everything goes right, rest of the time is much more relaxed. Doesn’t mean they’ll play table soccer for 2h, they can go back to work on other stuff.

As for why it’s difficult to implement patches that went live on kToS… language difference can ■■■■ things up in really subtle ways, they aren’t hosted on the same infrastructure which can change some behavior, there’s the interaction with Steam. Or the patch broke stuff on kToS, and the fix you did on the korean server don’t work on the english one.

2 Likes
#12

This post was flagged by the community and is temporarily hidden.

1 Like
#13

IMC takes shi* to a whole new level though.

Step1: Add 2 and a half hours to the maintenance after players are locked out of the game or locked into a specific channel and map for an additional 2 hours.

Step2: Extend the maintenance again by an additional 2 hours but do not tell the player base, simply edit the old maintenance message at the bottom.

Step3: Sit back and count the money while you watch the peasants qq on the forums.

1 Like
#14

I second that. Language difference can fudge stuff up in so many ways. Most of you think it’s just copy, paste and we’re done…! It’s not that simple guys/gals, just relax.

#15

no1 say its easy

but if u wanna put a pricetag to your service

u better be goddamn sure it works

hue

2 Likes
#16

Heh, he’s right about that. With these extensions it better work. Imagine if IMC applies and a player find a random exploit that was already fix before and they failed to back track? Ah disaster continues.

#17

This topic was automatically closed after 60 days. New replies are no longer allowed.