OVH Community, your new community space.

HA-Cluste Hibrido.


tonysanchez
12/05/2012, 14:28
Disponibilidad 100%

El rack de discos esta conectado a los 2 servidores que administran los discos y conectado a los 2 servidores que administran los discos: master y slave. En tiempo normal, es el master que da el servicio NFS/CIFS. En caso de problema en el master, el slave retoma immediatamente el servicio en los discos y comienza a dar el servicio NFS/CIFS. El cliente no constata ningún corte de acceso a los datos ni ninguna corrupción de ficheros
ping desde las 14:45 y cuyo resultado es que toda maquina que tenga este disco de mierda HA-Alta disponible 100% no funcionara...

21% de paquetes perdidos... COJONUDO.

Código:
root@mg01:~# ping 10.16.100.64
PING 10.16.100.64 (10.16.100.64) 56(84) bytes of data.
64 bytes from 10.16.100.64: icmp_req=2 ttl=251 time=36.7 ms
64 bytes from 10.16.100.64: icmp_req=3 ttl=251 time=39.3 ms
64 bytes from 10.16.100.64: icmp_req=4 ttl=251 time=35.4 ms
64 bytes from 10.16.100.64: icmp_req=9 ttl=251 time=35.0 ms
64 bytes from 10.16.100.64: icmp_req=10 ttl=251 time=36.2 ms
64 bytes from 10.16.100.64: icmp_req=11 ttl=251 time=21.6 ms
64 bytes from 10.16.100.64: icmp_req=13 ttl=251 time=24.8 ms
64 bytes from 10.16.100.64: icmp_req=14 ttl=251 time=32.5 ms
64 bytes from 10.16.100.64: icmp_req=15 ttl=251 time=31.4 ms
64 bytes from 10.16.100.64: icmp_req=17 ttl=251 time=33.3 ms
64 bytes from 10.16.100.64: icmp_req=18 ttl=251 time=34.2 ms
64 bytes from 10.16.100.64: icmp_req=19 ttl=251 time=23.5 ms
64 bytes from 10.16.100.64: icmp_req=20 ttl=251 time=24.1 ms
64 bytes from 10.16.100.64: icmp_req=24 ttl=251 time=22.8 ms
64 bytes from 10.16.100.64: icmp_req=25 ttl=251 time=24.9 ms
64 bytes from 10.16.100.64: icmp_req=26 ttl=251 time=32.2 ms
64 bytes from 10.16.100.64: icmp_req=27 ttl=251 time=25.5 ms
64 bytes from 10.16.100.64: icmp_req=28 ttl=251 time=25.2 ms
64 bytes from 10.16.100.64: icmp_req=30 ttl=251 time=24.5 ms
64 bytes from 10.16.100.64: icmp_req=31 ttl=251 time=24.2 ms
64 bytes from 10.16.100.64: icmp_req=32 ttl=251 time=28.8 ms
64 bytes from 10.16.100.64: icmp_req=34 ttl=251 time=26.2 ms
64 bytes from 10.16.100.64: icmp_req=36 ttl=251 time=26.8 ms
64 bytes from 10.16.100.64: icmp_req=37 ttl=251 time=25.2 ms
64 bytes from 10.16.100.64: icmp_req=38 ttl=251 time=22.4 ms
64 bytes from 10.16.100.64: icmp_req=39 ttl=251 time=22.6 ms
64 bytes from 10.16.100.64: icmp_req=40 ttl=251 time=23.7 ms
64 bytes from 10.16.100.64: icmp_req=41 ttl=251 time=26.3 ms
64 bytes from 10.16.100.64: icmp_req=42 ttl=251 time=27.7 ms
64 bytes from 10.16.100.64: icmp_req=43 ttl=251 time=24.3 ms
64 bytes from 10.16.100.64: icmp_req=44 ttl=251 time=28.3 ms
64 bytes from 10.16.100.64: icmp_req=45 ttl=251 time=22.6 ms
64 bytes from 10.16.100.64: icmp_req=46 ttl=251 time=24.5 ms
64 bytes from 10.16.100.64: icmp_req=48 ttl=251 time=24.3 ms
64 bytes from 10.16.100.64: icmp_req=49 ttl=251 time=24.3 ms
64 bytes from 10.16.100.64: icmp_req=50 ttl=251 time=39.2 ms
64 bytes from 10.16.100.64: icmp_req=51 ttl=251 time=36.5 ms
64 bytes from 10.16.100.64: icmp_req=52 ttl=251 time=29.0 ms
64 bytes from 10.16.100.64: icmp_req=53 ttl=251 time=29.9 ms
64 bytes from 10.16.100.64: icmp_req=54 ttl=251 time=37.7 ms
64 bytes from 10.16.100.64: icmp_req=55 ttl=251 time=21.4 ms
64 bytes from 10.16.100.64: icmp_req=56 ttl=251 time=26.9 ms
64 bytes from 10.16.100.64: icmp_req=57 ttl=251 time=23.4 ms
64 bytes from 10.16.100.64: icmp_req=58 ttl=251 time=25.5 ms
64 bytes from 10.16.100.64: icmp_req=59 ttl=251 time=25.4 ms
64 bytes from 10.16.100.64: icmp_req=60 ttl=251 time=25.4 ms
64 bytes from 10.16.100.64: icmp_req=62 ttl=251 time=26.0 ms
64 bytes from 10.16.100.64: icmp_req=63 ttl=251 time=29.0 ms
64 bytes from 10.16.100.64: icmp_req=64 ttl=251 time=32.0 ms
64 bytes from 10.16.100.64: icmp_req=65 ttl=251 time=22.1 ms
64 bytes from 10.16.100.64: icmp_req=66 ttl=251 time=36.5 ms
64 bytes from 10.16.100.64: icmp_req=67 ttl=251 time=21.2 ms
64 bytes from 10.16.100.64: icmp_req=68 ttl=251 time=29.4 ms
64 bytes from 10.16.100.64: icmp_req=69 ttl=251 time=32.9 ms
64 bytes from 10.16.100.64: icmp_req=70 ttl=251 time=40.5 ms
64 bytes from 10.16.100.64: icmp_req=71 ttl=251 time=28.0 ms
^C
--- 10.16.100.64 ping statistics ---
71 packets transmitted, 56 received, 21% packet loss, time 70059ms

tonysanchez
11/05/2012, 22:25
Bueno parace que se soluciono. A veces ya estoy susceptible.

Ciertamente el rendimiento de los nuevos hibrid es espectacular.


En cuanto a lo de nuevos... si miras als incidencias de RBX4 (firo/calor, red, etc) es un poco molesto .... y si añades que en un discode 1TB puedes tener unos cuantos VPS... pues muy muy molesto.

Saludos.

PacoSS
11/05/2012, 20:20
Eres el pupas, Tony.

Como dicen por aquí, te caes de espaldas y seguro que te partes la p*ya.

¿Como es posible eso? Se supone además que están en racks nuevos, etc, etc ...

tonysanchez
09/05/2012, 22:22
Sabia que la iba a cagar...

Tenia los normales, uno de 600, me paso a uno 1,2TB de los flamantes ha-Hybrid, y resulta que la red no pasa de 4Mbps de media...

El no Hibrid, no cache, no nada chupi del nuevo, media 50mbps...

Una vez mas, que la comi grande...