Project

General

Profile

Actions

Task #8858

closed

Monitor OrientDB instances

Added by Luca Frosini almost 8 years ago. Updated almost 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
_InfraScience Systems Engineer
Category:
System Application
Target version:
Start date:
Jun 06, 2017
Due date:
% Done:

100%

Estimated time:
Infrastructure:
Development, Production

Description

Orient DB instances must be monitored by using all oru checks: Ganglia, Munin, Nagios.

The nodes already appear in ganglia but under D4science Portals cluster for production and under D4Science Development servers for dev. I suggest to move them in a separated cluster if possible.

I didn't find any Munin monitoring.

I didn't find any Nagios Monitoring.

Actions #1

Updated by Luca Frosini almost 8 years ago

Please note that due to OrientDB bug I found we need to currently run with just one node.

https://github.com/orientechnologies/orientdb/issues/7354

I'm waiting for bug resolution from OrientDB team. If they don't solve the bug by the end of June I'll implement a workaround.

Actions #2

Updated by Andrea Dell'Amico almost 8 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 70

The nagios monitoring is active on orientdb01-d4s.d4science.org. In the next days I'll add a handler to manage the restart.

Ganglia will be in a massive reshaping in the next weeks: if a configuration that I'm going to test will work, there'll be no problem to create more clusters. Otherwise they will be collapsed even more, and the you will need to use the hostname as a filter.

Actions #3

Updated by Andrea Dell'Amico almost 8 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 70 to 100

The handler to manage the restarts has been added. On the parthenos instance too.

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 8.91 MB)