search for: downtimes

Hi, I need to get the exact downtime for doing a live migration with ms precision. (I am not bothered about whole migration time which is close to 1 minute.. I need to measure the live migration downtime during which the DomU is out of service.. the figure quoted in the xen documentation says it as ~60 ms.. ) I hope someone must have tried to measure this before. Can you suggest me ideas

What methods do people use to notify users of upcoming downtime in an application, and for handling requests nicely while scheduled downtime is occurring? My Google-fu is not yielding me anything useful-looking. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to

> Subject: Re: [PATCH v3 kernel 0/7] Extend virtio-balloon for fast (de)inflating > & fast live migration > > 2016-08-08 14:35 GMT+08:00 Liang Li <liang.z.li at intel.com>: > > This patch set contains two parts of changes to the virtio-balloon. > > > > One is the change for speeding up the inflating & deflating process, > > the main idea of this

> Subject: Re: [PATCH v3 kernel 0/7] Extend virtio-balloon for fast (de)inflating > & fast live migration > > 2016-08-08 14:35 GMT+08:00 Liang Li <liang.z.li at intel.com>: > > This patch set contains two parts of changes to the virtio-balloon. > > > > One is the change for speeding up the inflating & deflating process, > > the main idea of this

After a kernel update (but before rebooting) Is there a way to recompile Zap/Dahdi against the new kernel? My objective is to eliminate the additional downtime that occurs while recompiling/installing zap/dahdi after booting into the new kernel. Please correct me if I'm wrong: My understanding is that until you reboot (after a kernel update), recompiling zap/dahdi still compiles against

Hi there, I''ve read the paper on Xen live migration, and it shows some very impressive figures, like 165ms downtime on a running web server, and 50ms for a quake3 server. I installed CentOS 5 on 2 servers, each with 2x Xeon E5335 (quad-core), 2x Intel 80003ES2LAN Gb NICs. Then I installed 2 DomUs, also with CentOS 5. One NIC is connected to the LAN (on the same switch and VLAN), the

LLVMers, llvm.org will be down on 2/1 (approximate hours 10pm PST - ?), and 2/4 (8am PST - ?). Email will be sent to the list before and after the downtime. During this time ALL services (svn, web, etc) except for the mailing lists will be down. We are performing a server upgrade that will take some time, so I ask that you have patience. We will try to be as speedy as possible. Please let me

Hello, I have an imap server with huge Maildirs and several users running dovecot 1.0.13, I need to migrate all the imap accounts to a new box which runs dovecot 1.1.4. The requisite is that need to do it with no downtime or minimal downtime possible, and totally transparent for end users. I have tried IMAP<-->IMAP syncing using a master user in both servers and imapsync, however due

Hi, I have a setup with several dovecot-servers (2.2.35) and I use dovecot proxy. I upgraded one server to 2.3.1 and got the configs fixed so far that it started again. But when I tried to add it into the proxying again with "doveadm director add" I see the following in the logfiles: May 6 07:19:30 host dovecot: director: Warning: Director xxx.xxx.xxx.176:9090/out disconnected us with

Just a reminder, LLVM.org will be going down in 1 hour. Thank you, Tanya On Jan 28, 2013, at 2:28 PM, Tanya Lattner <lattner at apple.com> wrote: > To be clear: > Friday, February 1, 2013 & Monday, February 4, 2013 > > On Jan 28, 2013, at 2:08 PM, Tanya Lattner <lattner at apple.com> wrote: > >> LLVMers, >> >> llvm.org will be down on 2/1

llvm.org is now down. I will notify you when it is back up. This will take several hours. -Tanya On Feb 1, 2013, at 9:05 PM, Tanya Lattner <lattner at apple.com> wrote: > Just a reminder, LLVM.org will be going down in 1 hour. > > Thank you, > Tanya > > On Jan 28, 2013, at 2:28 PM, Tanya Lattner <lattner at apple.com> wrote: > >> To be clear: >>

To be clear: Friday, February 1, 2013 & Monday, February 4, 2013 On Jan 28, 2013, at 2:08 PM, Tanya Lattner <lattner at apple.com> wrote: > LLVMers, > > llvm.org will be down on 2/1 (approximate hours 10pm PST - ?), and 2/4 (8am PST - ?). Email will be sent to the list before and after the downtime. During this time ALL services (svn, web, etc) except for the mailing lists

> On 6 May 2018, at 8.46, Niels Kobsch?tzki <niels at kobschaetzki.net> wrote: > > Hi, > > I have a setup with several dovecot-servers (2.2.35) and I use dovecot > proxy. I upgraded one server to 2.3.1 and got the configs fixed so far > that it started again. But when I tried to add it into the proxying > again with "doveadm director add" I see the

Hello, there will be a downtime of the mail and list server tomorrow evening from around 20:00 UTC and a few (hopefully) hours after that. This means that there will be no mail traffic at that time to and from centos.org domains. We need to move away mail from the current machine to a new machine, as our old mailserver is a bit unreliable at the moment (the hardware is showing its age). After

Hello, I am now testing XEN live migration on 3 physical hosts with XEN 4.0.1 pvops Ubuntu 10.10 (2.6.35-22). The kernel is compiled and built with default selections plus the support for ext4 file system as well as the support for network file system server. The three hosts are connected by one D-link gigabit switch (DGS-2205). I find that: 1) If the 3 hosts are booted about the same time, the

Hello, there will be a downtime of the mail and list server tomorrow evening from around 20:00 UTC and a few (hopefully) hours after that. This means that there will be no mail traffic at that time to and from centos.org domains. We need to move away mail from the current machine to a new machine, as our old mailserver is a bit unreliable at the moment (the hardware is showing its age). After

--GYkYyJI7bObpCn+O Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! Due to an unfortunate event [*] the main netfilter.org system had become unavailable from Aug 19 to Aug 22. =20 The long downtime was caused by the netfilter developer workshop, which distracted the netfilter developers from doing any system administration.

Dear LLVMers, The LLVM mailing lists will be down on December 18 at 2:00 pm and is expected to be back up around 2:30 pm. The full description from TSG is as follows: On Monday, December 18, 2006 starting at 2:00 pm, the server that hosts the Mailman mailing lists will be unavailable while we replace bad memory. During the hardware replacement, the Mailman web interface, archives,

Dear All, On Monday, March 17, the computer science building will have its cooling system turned off for maintenance. During that time, the offices and computer labs in the building may get warm, and as a consequence, we may need to power off machines. While I am hoping that down time will be unnecessary, we may need to power down llvm.org during the cooling outage. It is also possible

***Do you perform downtimes just for the purpose of rebooting the systems? ***Is there a recommended interval Linux system should be rebooted? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20050602/189d0dbf/attachment-0004.html>