All about incidents

Salma Hayek's cup runneth over (Almost)

Foot - MAR - Près de quarante supporters blessés

Des juristes repondent à vos questions sur Internet

technicien hotline niveau 1 h/f

technicien - analyste d'exploitation unix / mvs h/f

My node was equipped with the following...

eve-online.com | devBlog

- 7 hours and 54 minutes ago

Gentlemen!

I thought I would add to the recent dev blogs we have had over the last couple of weeks and talk about what has been going on with the Tranquility cluster itself - in relation to the StacklessIO and 64-bit EVE enhancements and where we are heading into the future.

1 x EVE Server Cluster

The EVE Cluster is broken into 3 distinct layers, and a bit of the terminology that is thrown around from time to time (including later in this blog) can be explained quite simply here.

Proxy Blades- These are the public facing segment of the EVE Cluster - they are responsible for taking player connections and establishing player communication within the rest of the cluster.
SOL Blades - These are the workhorses of Tranquility and are the primary focus of our ongoing work. The cluster is divided across 90 - 100 SOL blades which run 2 nodes each.
- Node - a single EVE server process. This is the lowest level of granularity within the cluster.
- Dedicated SOL blade - These are SOL blades that we dedicate to one system only. Systems such as Jita, Motsu and Saila reside on these. They run two nodes like any other SOL blade, however the second node is idle and does not load any solar systems.
Database Cluster - This is the persistence layer of EVE Online. The running nodes interact heavily with the Database, and of course pretty much everything to do with the game lives here. Thanks to our RamSans, our database is able to keep up with the enormous I/O load that Tranquility generates.
- At peak hours, our database is processing over 2,000 transactions per second, which generates around 38,000 IOPS (input output operations per second)
- To keep up with this load, we currently have two RamSans.

1 x SOL Blade

The EVE Server application itself (also known as a node) is primarily a CPU intensive process. Due to the nature of the Stackless Python programming methodology chosen for EVE Online, the python component of each node is a single thread, which means it can only ever utilize 1 CPU core at a time.

Our SOLs are IBM blades, and up until quite recently were almost all running AMD Opteron 2.8Ghz Dual Core processors with 4GB of DDR1 Ram. Over the last 6 months or so, we have been investigating options for replacing these Opteron processors with something more powerful. We selected some dual socket, dual core Intel Xeon 3.0Ghz Woodcrest blades for testing purposes, and have been using them as an integral part of our StacklessIO testing (as blogged about here by CCP Explorer). Now that StacklessIO has been released we are able to use these blades to their fullest, and as a first step looked at ways we could use these test blades on Tranquility.

1 x Rapid Deployment

When we hit 1400 players in Jita and then had the unfortunate incident where the SOL blade powering Jita ran out of memory, we looked to our Intel test blades for help. We shuffled some RAM around and were able to get 5 new Intel SOL blades with 16Gb of DDR2 Ram each ready for use. We did a staggered test deployment of these to Tranquility last week. On Friday, confident of their stability and anticipating performance increases, we set them up as dedicated SOL blades. That evening, Jita, Saila and Motsu were performing better than ever, and there was much rejoicing. Over the last weekend, the GM's did not receive a single "Stuck Character" petition from Jita!

3 x Epic Fleet Fights

That Saturday, out of the blue we saw one of the nodes supporting 0.0 go to Critical status and shortly afterwards it shut down. This happened a few more times in quick succession, and it became apparent that there was a new issue where extremely loaded nodes were simply not able to keep up with their heartbeat. This issue in itself is fixable and we are working hard to get it resolved.

At this point, it was apparent that with 700+ players trying to "pew pew", the AMD node they were on was not going to do anything other than keep crashing. We re-mapped the system in question to one of our dedicated Intel blades, just to see what it was capable of. Jita had performed so well the night before, that we thought these nodes would handle a fleet fight quite nicely. The system held, and the rest, as they say, is history.

On Sunday night, the M-OEE8 System was the hotspot and it had been placed on an Intel 64 bit dedicated SOL blade in anticipation. It held fine with a peak of around 450 players.

On Monday night, over 1000 players tried to start a fight in this system. As with Sunday, we had anticipated there would be fighting there, so it had been placed on a dedicated node. Unfortunately, what had caused node crashes at 700 players on our AMD blades caused our Intel blade to miss its heartbeat after going a bit over 1200 players. Interestingly enough, despite missing its heart beat, many players have reported that the performance of this blade with 1000 players was very good in the 10 - 15 minutes prior to its shutdown.

I would like to stress that we at CCP are very excited by this, and we are very hopeful that once the issue causing these node deaths is solved that we will start to see this impressive performance much more often. A lot of people have put in a lot of hard work towards new technologies and it is starting to pay off for you, the players.

So where do we go from here?

We are by no means finished with these upgrades, and there is still a lot of work to be done. During this last two week period, we have proved the readiness of some of our new technology, and we now need to work on the best way to ensure everyone can benefit...

Newer, Faster Blades

Our 3.0Ghz Intel Woodcrest blades are nice, but that processor architecture has been replaced by Wolfdale, which is even more powerful. So we have put a fast-track order in for some Intel Xeon 3.3Ghz Wolfdale blades. We expect to have these in the cluster very soon and we anticipate these will give us an even bigger performance boost than we have seen so far, paving the way for a new Tranquility Cluster. It is worth noting that the hardware we are beginning to purchase now is the hardware that will see us all the way into the HPC era. There will be a detailed presentation about the status of this project at Fanfest in November.

Help us to help you

It's nice that we have this new hardware, but there is going to be an interim period while we work to upgrade the existing hardware to this HPC-ready specification. During this period, we will be proactively working to place fleet fight systems onto a dedicated node at downtime. We often can't predict where our players are planning to unleash hell, so we need to know which systems are going to have fleet fights! We are working on a way to allow players to directly contact the Virtual World Operations team with this information, however in the mean time corporation directors are invited to petition any planned operations (use the Stuck Character category at least 24 hours in advance, and please include estimated attack / defense numbers), and we will take note of this when we assign systems to dedicated sol blades during downtime.

With that, I will leave you with my final - subtle - personal thoughts on the matter.

This is EVE Online!

Impossible is nothing!

Add a comment

mondays,crashes,threads,performances,hopeful

ingenieur unix

La direction de l’ICDI a organisé son piquet de grève!

tech helpedesk bilingue h/f

Day 6 - Network-based Intrusion Detection Systems, (Mon, Oct 6th)

administrateur systeme linux/vmware

dba oracle

13:09 Un manifestant renversé à Verviers

13:01 Verviers : un manifestant renversé

Voyeuristic landlord spied on female tenants

superviseur telecom (h/f)

Annonces lesjeudis.com

- 13 hours and 36 minutes ago

Societe : ESR - Lieu de travail : IDF - Type de contrat : CDI - Salaire : 25-30KEuros - Detail : Contexte : Les superviseurs assurent 24h/24 7j/7 la disponibilité et la surveillance du périmètre défini, en garantissant le niveau et les engagements de service ainsi que la qualité des traitements conformément au plan d'assurance qualité et de sécurité. Mission : ►Supervision du Réseau 2G/3G R4 et core paquet suivants les engagements des contrats de service : ▪Détecter. ▪ Analyser, diagnostiquer. ▪Créer un ticket dans l'outil de gestion des incidents. ▪Gérer les tickets crées dans l'outil de gestion des incidents. ▪Appliquer les fiches de consignes liées aux incidents. ▪Orienter le dysfonctionnement si la résolution n'est pas formalisée par une consigne. ▪ Procéder aux escalades en cas de nécessité. ►Ventilation et suivi des incidents non résolus transmis aux tiers (services client, mainteneurs,?). ▪Prendre en charge les incidents de la chaîne de soutien. ▪ Appliquer les procédures correctives. ▪ Tracer l'incident dans l'outil de gestion des incidents. ▪Suivre l'évolution de la résolution de l'incident dans le cas d'une escalade vers le niveau supérieur de la chaîne de soutien. ►Reporting des actions réalisées dans l'outil de gestion des incidents (cause de la panne, dates d'intervention, actions réalisées). ►Participer à la configuration management et aux intégrations d'éléments. ►Suivre les actions de maintenance ainsi que les interventions planifiées. Les compétences suivantes sont requises : ▪Connaissances bureautiques Windows. ▪Expertise des méthodes, systèmes et outils de production réseau Télécoms (SGSN 2G/3G). ▪Connaissance des réseaux IP. ▪Connaissance des outils NetAct, Flexi ISN. PROFIL: ▪Formation initiale - Bac + 2. ▪Expérience - 2 ans dans le domaine de la production. QUALITES REQUISES: ▪Autonomie et rigueur. ▪Capacité d'écoute et de communiquer. ▪Sens du service et de la relation client. ▪Disponibilité, capacité à gérer les situations d'urgence et de stress. ▪Adaptabilité, anticipation, réactivité. ▪Gestion des priorités et des escalades. ▪Rigueur, méthode, organisation.

Add a comment

domaines,2g,telecom,incidents,organisations

cdi 75 client final dba oracle et sql server leader dans son domaine (h/f)

Annonces lesjeudis.com

- 14 hours and 19 minutes ago

Societe : PROGRESSIVE - Lieu de travail : CDI 75 Client Final DBA Oracle et Sql Server Leade - Type de contrat : CDI - Salaire : Negotiable - Detail : Administrateur Base de données (Oracle et SQLServer) Rattaché au Responsable DBA vous assurerez la bonne exécution des missions telles que: L’administration des bases de données Oracle (Développement, recette et production) en environnement Unix et Windows, L’installation et de la mise à jour des SGBD, L’analyse et l’amélioration des performances des différents SGBD en veillant à l’intégrité et à la cohérence des données, (Tuning) Le support technique de niveau 2 sur les SGBD, La réalisation des documentations et des procédures nécessaires, L’administration des environnements Oracle Applications développement, recette et production (OA) en particulier : o La préparation des instances OA (création d’un nouvel environnement), o La configuration des instances OA (passage de patchs, ajout de modules, ...), o Les mises en production sur les environnements, o Le clonage et le rafraîchissement des environnements, La participation à la gestion des incidents et des changements Le reporting de son activité. Il assurera aussi L’administration des bases de données SQL Server 7, 2000 et 2005 en relation avec le responsable des systèmes Le salarié assurera aussi : les missions et tâches de son responsable pendant ses absences. le rôle d’interface au quotidien des autres équipes de la DSI. Il apportera aussi le support technique aux Chefs de projets fonctionnels de la DSI et à l’ensemble des équipes d’infrastructure dans le cadre des environnement sous Oracle. Dans le cadre de sa mission ou de nouveaux projets, le Salarié sera en relation avec d’autres collaborateurs de la DSI et/ou des prestataires. Il réalisera dans ce cas le transfert de compétences si nécessaire, le reporting de cette activité auprès du projet concerné et de la DSI. Le profil doit avoir le sens aiguë de la production et de la qualité de service qui est l’axe majeur de la mesure de la performance individuelle. Localisation Le poste est basé au siège à Paris avec des déplacements limités en banlieue parisienne et en province. Niveau Bac + 4 cursus scolaire informatique Expérience Vous avez au minimum 2 ans d’expérience dans l’administration des bases de données Connaissances indispensables .... SGBD Oracle 9i, Oracle 9I Tuning SQL Server 7, 2000 et 2005 Connaissance souhaitée .... Oracle 10g souhaitable Oracle Applications 11.5.9 Connaissance souhaitée du réseau TCP/IP, DNS et WINS Langue Anglais lu couramment Personnalité Goût du travail en équipe Très bon relationnel Rigueur Autonomie dans le travail Pro-activité, réactivité Qualité rédactionnelle Gestion du stress Avantage de ce CDI: - Montée en puissance sur Oracle Application - Cadre agréabe - DSI en croissance - Grande entreprise qui maintient un management de proximité. - Secteur d’activité porteur

Add a comment

particuliers,domaines,grande entreprise,performances,patchs

Shooting ruins VWF London event

Lyon : le mail des RG, réactions en chaîne - LyonGratuit.com