Project

General

Profile

Actions

Task #3475

closed

Add 2 OrientDB instances

Added by Luca Frosini about 9 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Normal
Category:
Application
Start date:
Sep 29, 2016
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Infrastructure:
Development

Subtasks 1 (0 open1 closed)

Task #5227: Enable SSL on the orientdb instancesClosedAndrea Dell'AmicoSep 29, 2016

Actions

Related issues

Related to D4Science Infrastructure - Task #4984: Create new VM to host new Resource RegistryClosedAndrea Dell'AmicoSep 09, 2016Sep 13, 2016

Actions
Related to D4Science Infrastructure - Task #5568: Please Update orientdb version to 2.2.12Closed_InfraScience Systems EngineerOct 26, 2016

Actions
Actions #1

Updated by Luca Frosini about 9 years ago

  • Parent task set to #3474
Actions #2

Updated by Luca Frosini about 9 years ago

  • Tracker changed from Support to Task
Actions #3

Updated by Luca Frosini about 9 years ago

  • Start date changed from Apr 15, 2016 to Mar 07, 2016
Actions #4

Updated by Luca Frosini almost 9 years ago

  • Due date set to Mar 11, 2016

I'll provide configuration information in the next days

Actions #5

Updated by Luca Frosini almost 9 years ago

  • Subject changed from Add other 2 OrientDB instances to Add 2 OrientDB instances

There are 3 file to be configured through ansible scripts:

  • ~/orientdb-community-2.1.13/config/orientdb-server-config.xml
  • ~/orientdb-community-2.1.13/config/hazelcast.xml
  • ~/orientdb-community-2.1.13/config/default-distributed-db-config.json

I propose to start in the following way:
I would like test the cluster so that adding a new server instance must not imply to restart the others (especially on production). To accomplish this we can configure hazelcast to use:

  • multicast
  • encryption on server synchronizations.

Due to actual sharding limitations (http://orientdb.com/docs/last/Distributed-Sharding.html#limitation) I would like to avoid it (seems that they will improve this part in the next version 2.2).

In particular:

Regarding orientdb-server-config.xml:

<parameter name="enabled" value="true" /> 
  • You can decide if you want to store the admin password as plain text or as hash:
<user resources="*" password="7EA0EAF7FCCECA5C5B261B69CD8EC0F725FB8B3102AF51A4033CC3DED22EBD8A" name="root"/>
<user resources="*" password="PlainPassword" name="root"/>
  • Please note that during the development I will have the need to modify this configuration by adding tag. An example can be:
<hooks>
   <hook class="org.gcube.informationsystem.hooks.DocumentHook" position="REGULAR"/>
   <hook class="org.gcube.informationsystem.hooks.RecordHook" position="REGULAR"/>
</hooks>

Regarding hazelcast.xml:

Regarding default-distributed-db-config.json please remove clusters property.

More details can be found here:
http://orientdb.com/docs/last/Distributed-Configuration.html

Feel free to contact me for any doubt.

Actions #6

Updated by Luca Frosini almost 9 years ago

Can you also create a txt DNS record as described here:
http://orientdb.com/docs/last/Distributed-Configuration.html#use-the-dns

Actions #7

Updated by Luca Frosini almost 9 years ago

  • Priority changed from Normal to High
Actions #8

Updated by Luca Frosini almost 9 years ago

  • Parent task changed from #3474 to #3897
Actions #10

Updated by Luca Frosini almost 9 years ago

  • Priority changed from High to Urgent
Actions #11

Updated by Tommaso Piccioli almost 9 years ago

  • Assignee changed from _InfraScience Systems Engineer to Luca Frosini
  • % Done changed from 0 to 60

orientdb01-d-d4s.d4science.org 146.48.122.23
orientdb02-d-d4s.d4science.org 146.48.122.14
orientdb03-d-d4s.d4science.org 146.48.122.148

No ansible at the moment for the orientdb/hazelcast configuration, it will be done later, please configure the cluster by hand if you want to test it.

You can connect via ssh as orientdb user and manage orientdb service with
/home/orientdb/orientdb start/stop/status

Actions #12

Updated by Luca Frosini almost 9 years ago

  • Status changed from New to In Progress

Ok. I'll take care of configuring the cluster.

Actions #13

Updated by Luca Frosini almost 9 years ago

  • Assignee changed from Luca Frosini to Tommaso Piccioli

@tommaso.piccioli@isti.cnr.it I need your support to correctly configure hazelcast.

Actions #14

Updated by Luca Frosini almost 9 years ago

  • Assignee changed from Tommaso Piccioli to _InfraScience Systems Engineer

Can you configure hazelcast with static hostnames? We will try multicast in the future.

Actions #15

Updated by Luca Frosini almost 9 years ago

  • % Done changed from 60 to 100
Actions #16

Updated by Luca Frosini almost 9 years ago

  • Status changed from In Progress to Closed
Actions #17

Updated by Luca Frosini over 8 years ago

  • Status changed from Closed to In Progress
  • Priority changed from Urgent to Normal
  • Target version changed from OrientDB Assessment to Dev Resource Registry Deployment
  • % Done changed from 100 to 70

We need to setup OrientDB cluster with the 3 VMs available

Actions #18

Updated by Andrea Dell'Amico over 8 years ago

  • Related to Task #4984: Create new VM to host new Resource Registry added
Actions #19

Updated by Andrea Dell'Amico over 8 years ago

  • Assignee changed from _InfraScience Systems Engineer to Andrea Dell'Amico
  • % Done changed from 70 to 50

I'm assembling a oriendb ansible role to provision all the pieces.

Actions #20

Updated by Andrea Dell'Amico over 8 years ago

  • % Done changed from 50 to 90

The playbook is ready and the configuration seems corret. We have errors on the hooks, because we didn't create the rules that install the needed jars. I need directions for those.

Actions #21

Updated by Andrea Dell'Amico over 8 years ago

We also need to tweak the java heap configuration.

Actions #22

Updated by Luca Frosini over 8 years ago

Andrea Dell'Amico wrote:

The playbook is ready and the configuration seems corret. We have errors on the hooks, because we didn't create the rules that install the needed jars. I need directions for those.

The jar file is available here:
http://maven.research-infrastructures.eu/nexus/service/local/artifact/maven/redirect?r=gcube-snapshots&g=org.gcube.information-system&a=resource-registry-orientdb-hooks&v=1.0.0-SNAPSHOT&e=jar&c=jar-with-dependencies

Maven coordinates:

<groupId>org.gcube.information-system</groupId>
<artifactId>resource-registry-orientdb-hooks</artifactId>
<version>1.0.0-SNAPSHOT</version>

The jar must be copyed in $ORIENTDB_HOME/lib. Every time the lib is changed orient must be restarted.

Class to be included in orientdb-server-config.xml is org.gcube.informationsystem.orientdb.hooks.HeaderHook.
The result in orientdb-server-config.xml must be :

<hooks>
    <hook class="org.gcube.informationsystem.orientdb.hooks.HeaderHook" position="REGULAR"/>
</hooks>
Actions #23

Updated by Andrea Dell'Amico over 8 years ago

  • Status changed from In Progress to Feedback
  • % Done changed from 90 to 100

Done. The hook has been installed, the configuration updated, the services restarted.

Actions #24

Updated by Andrea Dell'Amico over 8 years ago

The java heap is now configurable. I've set it to 2048MB.

Actions #25

Updated by Luca Frosini over 8 years ago

  • Status changed from Feedback to Closed
Actions #26

Updated by Luca Frosini over 8 years ago

  • Status changed from Closed to In Progress
Actions #27

Updated by Luca Frosini over 8 years ago

  • Related to Task #5568: Please Update orientdb version to 2.2.12 added
Actions #28

Updated by Andrea Dell'Amico about 8 years ago

  • Status changed from In Progress to Closed
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 8.91 MB)