
Registered since September 28th, 2017
Has a total of 4281 bookmarks.
Showing top Tags within 2 bookmarks
howto information development guide reference administration design website software solution online service product business uk tool company linux code server application system web list video marine create data experience tutorial description explanation learn technology build article blog world project boat download windows lookup security free performance javascript technical london beautiful control network tools support course file research purchase image library programming youtube example php construction install opensource community html quality computer feature profile power browser music platform process mobile work user share manage professional database hardware buy industry advice internet dance developer installation 3d search camera access customer travel material standard money test develop review documentation css engineering photography webdesign engine device digital speed event api source management program question client phone discussion content simple story water marketing yacht app account setup interface package idea fast communication compare cheap script market study easy live google resource operation demonstration contact startup
Tag selected: reboot.
Looking up reboot tag. Showing 2 results. Clear
Saved by uncleflo on February 26th, 2018.
At work, we run a simple high-availability (HA) MariaDB setup that consists of an active master that handles all read and write queries from our applications, a passive master that can take over for the active master at any time, and a read-only replication slave (not shown) that we use for backups and analytics. Replication is configured so that the active master follows the passive master, the passive master follows the active master, and the analytics slave follows one of the masters. For the remainders of this post, I will refer to the active master as the master and the passive master as the standby. The benefits of this master-master configuration is that it allows us not only to failover from master to standby if the master becomes unhealthy, but also allows us to perform patching, reboots, lengthy migrations, and other kinds of database maintenance without impacting our users. Well, almost...
high availability mariadb master slave query db dbms backup replication failover painless administration configuration perform patch reboot application remain impact user configure maintain
Saved by uncleflo on June 10th, 2015.
In previous versions of Windows, you probably remember the good ol paging file. It’s used to when physical memory becomes overcommitted and it hold objects that usually have not been accessed in a long time. That is pagefile.sys. Next, we had the hibernate option in Windows that let you save the kernel and all applications to your hard drive so that you could start your computer back up faster than doing a full reboot. That is hiberfile.sys.
windows swapfile hiberfil hyper file file hyper space system memory reboot kernel paging operating information guide explanation startup administration
No further bookmarks found.