search for: mttr

...d Windows servers? Here are my requirements: SNMP trap collection, ability to import custom MIBs isup/isdown monitoring of ports and daemons Server health monitors (CPU, Disk, Memory, etc) SLA reporting with nice graphs Pager/Email/SMS alerts with groups, filters and escalations Built-in MTBF and MTTR reporting Robust parent-child relationships between monitors or probes. For example, the system must be smart enough to know that if 25 URLs have gone down all at once, that they belong to an apache process that has died. I don't want 25 alerts, I want *one* alert telling me that the parent a...

...ar mejores precios comprando "10" que "1".Entonces por este lado, tener en tu almacén un número constante de "3". Y que ese sea tu punto de pedido no parece descabellado. Otra forma de analizarlo teniendo en cuenta los datos que ya has acumulado es ver cuál es tu "MTTR" (Mean Time To Repair). Considera la rotura/desgaste de la cuchilla como una "reparación". Y con este concepto calcula el tiempo medio que pasa hasta que sustituyes una cuchilla. Esto lo puedes calcular con los datos que tienes, simplemente calculando las diferencias entre las fechas...

...do "10" que "1". - Entonces por este lado, tener en tu almacén un número constante de "3". Y que ese sea tu punto de pedido no parece descabellado. - Otra forma de analizarlo teniendo en cuenta los datos que ya has acumulado es ver cuál es tu "MTTR" (Mean Time To Repair). Considera la rotura/desgaste de la cuchilla como una "reparación". Y con este concepto calcula el tiempo medio que pasa hasta que sustituyes una cuchilla. Esto lo puedes calcular con los datos que tienes, simplemente calculando las diferencias entr...

...mail.com CC: r-help-es en r-project.org Hola, Puedes adjuntar una parte o el conjunto "datos". Ahora no sé si los datos que quieres representar tienen que ver con el conjunto que nos comentabas de las cuchillas. ¿Hay diferentes tipos de cuchillas?... En cuanto al consumo, ¿calculaste el MTTR?... Y por otro lado, respondiendo a la pregunta que planteas, si ves la ayuda de "hist()" verás que lo que acepta esta función, sólo acepta un vector como parámetro de entrada, no una lista. Saludos, Carlos Ortega www.quallityexcellence.es El 10 de diciembre de 2015, 19:04, Jesús Pa...

Since memory has become quite cheap lately I decided to move from 2 GB to 6. When I installed the memory every thing was fine until I went to run level 5. At that point the screen turned to garbage and the system froze. Is there a way to fix this so I can use the memory I bought? Do I need a new display card? Current hardware: Intel D975XBX2 Motherboard VGA compatible controller: ATI

Se ha borrado un adjunto en formato HTML... URL: <https://stat.ethz.ch/pipermail/r-help-es/attachments/20151210/04bc012e/attachment-0001.html>

for s10u2, documentation recommends 3 to 9 devices in raidz. what is the basis for this recommendation? i assume it is performance and not failure resilience, but i am just guessing... [i know, recommendation was intended for people who know their raid cold, so it needed no further explanation] thanks... oz -- ozan s. yigit | oz at somanetworks.com | 416 977 1414 x 1540 I have a hard time

The reason for the long (42 second) ping-timeout is because re-establishing fd's and locks can be a very expensive operation. With an average MTBF of 45000 hours for a server, even just a replica 2 would result in a 42 second MTTR every 2.6 years, or 6 nines of uptime. On December 27, 2017 3:17:01 AM PST, Omar Kohl <omar.kohl at iternity.com> wrote: >Hi, > >> If you set it to 10 seconds, and a node goes down, you'll see a 10 >seconds freez in all I/O for the volume. > >Exactly! ONLY 10 seconds...

...1:08 am, Joe Julian <joe at julianfamily.org> wrote: > > The reason for the long (42 second) ping-timeout is because re-establishing fd's and locks can be a very expensive operation. With an average MTBF of 45000 hours for a server, even just a replica 2 would result in a 42 second MTTR every 2.6 years, or 6 nines of uptime. > > On December 27, 2017 3:17:01 AM PST, Omar Kohl <omar.kohl at iternity.com> wrote: > Hi, > > If you set it to 10 seconds, and a node goes down, you'll see a 10 seconds freez in all I/O for the volume. > > Exactly! ONLY 10...

...ly.org>> wrote: >> >> The reason for the long (42 second) ping-timeout is because >> re-establishing fd's and locks can be a very expensive operation. >> With an average MTBF of 45000 hours for a server, even just a replica >> 2 would result in a 42 second MTTR every 2.6 years, or 6 nines of uptime. >> >> On December 27, 2017 3:17:01 AM PST, Omar Kohl >> <omar.kohl at iternity.com <mailto:omar.kohl at iternity.com>> wrote: >> >> Hi, >> >> If you set it to 10 seconds, and a node goes down,...

On Apr 18, 2007, at 6:44 AM, Yaniv Aknin wrote: > Hello, > > I''d like to plan a storage solution for a system currently in > production. > > The system''s storage is based on code which writes many files to > the file system, with overall storage needs currently around 40TB > and expected to reach hundreds of TBs. The average file size of the >

...ulianfamily.org <mailto:joe at julianfamily.org> > wrote: The reason for the long (42 second) ping-timeout is because re-establishing fd's and locks can be a very expensive operation. With an average MTBF of 45000 hours for a server, even just a replica 2 would result in a 42 second MTTR every 2.6 years, or 6 nines of uptime. On December 27, 2017 3:17:01 AM PST, Omar Kohl <omar.kohl at iternity.com <mailto:omar.kohl at iternity.com> > wrote: Hi, If you set it to 10 seconds, and a node goes down, you'll see a 10 seconds freez in all I/O for the...

Hi, I''m struggling to get a stable ZFS replication using Solaris 10 110/06 (actual patches) and AVS 4.0 for several weeks now. We tried it on VMware first and ended up in kernel panics en masse (yes, we read Jim Dunham''s blog articles :-). Now we try on the real thing, two X4500 servers. Well, I have no trouble replicating our kernel panics there, too ... but I think I

Hi, > If you set it to 10 seconds, and a node goes down, you'll see a 10 seconds freez in all I/O for the volume. Exactly! ONLY 10 seconds instead of the default 42 seconds :-) As I said before the problem with the 42 seconds is that a Windows Samba Client will disconnect (and therefore interrupt any read/write operation) after waiting for about 25 seconds. So 42 seconds is too high. In

Hi, i have a problem with xen. the output of uname is:Linux xen 2.6.12-gentoo-r6 #9 SMP Mon Jan 23 18:13:25 CET 2006 i686 AMD Opteron(tm) Processor 844 AuthenticAMD GNU/Linux i user the SAME config of the kernel, for xen0 domain, and when i boot with xen0 kernel it reboots after this output... . . . ipt_recent v0.3.1: Stephen Frost <sfrost@snowman.net>.

Which consumer-priced 1.5TB drives do people currently recommend? I had zero read/write/checksum errors so far in 2 years with my trusty old Western Digital WD7500AAKS drives, but now I want to upgrade to a new set of drives that are big, reliable and cheap. As of Jan 2010 it seems the price sweet spot is the 1.5TB drives. As I had a lot of success with Western Digital drives I thought I would

ZFS fans, I''m preparing some analyses on RAS for large JBOD systems such as the Sun Fire X4500 (aka Thumper). Since there are zillions of possible permutations, I need to limit the analyses to some common or desirable scenarios. Naturally, I''d like your opinions. I''ve already got a few scenarios in analysis, and I don''t want to spoil the brain storming, so