
Registered since September 28th, 2017
Has a total of 4246 bookmarks.
Showing top Tags within 2 bookmarks
howto information development guide reference administration design website software solution service product online business uk tool company linux code server system application web list video marine create data experience description tutorial explanation technology build article blog learn world project boat download windows security lookup free performance javascript technical control network beautiful london support tools course file research purchase library programming image youtube example php construction html quality install community opensource computer profile feature power browser music platform mobile user process work database share manage hardware professional buy industry internet dance advice installation developer 3d material access customer travel camera search test standard review documentation css money engineering develop webdesign engine device photography source digital api speed management program discussion question event phone simple client story water marketing app content yacht setup package interface fast idea account cheap communication compare script study live easy market google resource operation monitor startup price
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.