{"id":1526,"date":"2024-09-17T14:59:35","date_gmt":"2024-09-17T12:59:35","guid":{"rendered":"https:\/\/spgoo.org\/?page_id=1526"},"modified":"2024-09-17T15:44:03","modified_gmt":"2024-09-17T13:44:03","slug":"clutser-neo4j","status":"publish","type":"page","link":"https:\/\/spgoo.org\/?page_id=1526","title":{"rendered":"Cluster – Neo4j"},"content":{"rendered":"\n

Fiche de configuration d’un cluster dans le cadre d’EMOLGINE 2024 <\/p>\n\n\n\n

Dans le cadre du projet Emolgine, nous allons mettre en oeuvre un cluster Neo4J<\/span> afin d’estimer les besoins n\u00e9cessaires \u00e0 la manipulation de quelques milliards de mol\u00e9cules. L’architecture mise en place est compos\u00e9e de trois VMs de 60 Go de disque et de 16 Go de Ram avec 4 cores sur un r\u00e9seau d\u00e9di\u00e9 192.168.100.0\/24. <\/p>\n\n\n\n

Installation de 3 Vms de 16 Go et 4 cores avec Ubuntu 24.04 avec arborescence suivante <\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

Arborescence des fichiers sur chaque machine.<\/p>\n\n\n\n

\n
\n

Neo4J<\/span>
R\u00e9pertoire contenant l’archive de la version community

R\u00e9pertoire contenant les fichiers de param\u00e9trage de Neo4J<\/span>


Script de lancement de l’instance
Script de chargement de la base
R\u00e9pertoire qui va contenir les fichiers des bases<\/p>\n<\/div>\n\n\n\n

\n
Neo4J<\/span>\n\u251c\u2500\u2500 \/backups\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 Neo4J<\/span>.dump\n\u251c\u2500\u2500 \/conf \n\u2502\u00a0\u00a0 \u251c\u2500\u2500 Neo4J<\/span>-admin.conf\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 Neo4J<\/span>.conf\n\u2502\u00a0\u00a0 \u251c\u2500\u2500 server-logs.xml\n\u2502\u00a0\u00a0 \u2514\u2500\u2500 user-logs.xml\n\u251c\u2500\u2500 lance_conf.sh  \n\u251c\u2500\u2500 lance_load.sh  \n\u251c\u2500\u2500 \/newdata <\/code><\/pre>\n<\/div>\n<\/div>\n\n\n\n
<\/p>\n\n\n\n
Script de d\u00e9marrage des instances de Neo4J<\/span> enterprise 5.23.0 : lance_conf.sh<\/p>\n\n\n\n
\n
\n
!#\/bin\/bash\ndocker run --name=server1 -d \\\n--network=host \\\n-p 7474:7474 -p 7687:7687 \\\n-p 5000:5000 -p 6000:6000 -p 7000:7000 \\\n--hostname=192.168.100.220 \\\n--env Neo4J<\/span>_ACCEPT_LICENSE_AGREEMENT=eval \\\n-v \/home\/ystroppa\/Neo4J<\/span>\/newdata:\/var\/lib\/Neo4J<\/span>\/data \\\n-v \/home\/ystroppa\/Neo4J<\/span>\/conf:\/var\/lib\/Neo4J<\/span>\/conf \\\nNeo4J<\/span>:5.23.0-enterprise<\/code><\/pre>\n<\/div>\n\n\n\n
\n
!#\/bin\/bash\ndocker run --name=server1 -d \\\n--network=host \\\n-p 7474:7474 -p 7687:7687 \\\n-p 5000:5000 -p 6000:6000 -p 7000:7000 \\\n--hostname=192.168.100.221 \\\n--env Neo4J<\/span>_ACCEPT_LICENSE_AGREEMENT=eval \\\n-v \/home\/ystroppa\/Neo4J<\/span>\/newdata:\/var\/lib\/Neo4J<\/span>\/data \\\n-v \/home\/ystroppa\/Neo4J<\/span>\/conf:\/var\/lib\/Neo4J<\/span>\/conf \\\nNeo4J<\/span>:5.23.0-enterprise<\/code><\/pre>\n<\/div>\n\n\n\n
\n
!#\/bin\/bash\ndocker run --name=server1 -d \\\n--network=host \\\n-p 7474:7474 -p 7687:7687 \\\n-p 5000:5000 -p 6000:6000 -p 7000:7000 \\\n--hostname=192.168.100.222 \\\n--env Neo4J<\/span>_ACCEPT_LICENSE_AGREEMENT=eval \\\n-v \/home\/ystroppa\/Neo4J<\/span>\/newdata:\/var\/lib\/Neo4J<\/span>\/data \\\n-v \/home\/ystroppa\/Neo4J<\/span>\/conf:\/var\/lib\/Neo4J<\/span>\/conf \\\nNeo4J<\/span>:5.23.0-enterprise<\/code><\/pre>\n<\/div>\n<\/div>\n\n\n\n
Contenu du fichier \/conf  4 fichiers <\/p>\n\n\n\n
Neo4J<\/span>-admin.conf : par d\u00e9faut<\/p>\n\n\n\n
server-logs.xml: par d\u00e9faut<\/p>\n\n\n\n
user-logs.xml: par d\u00e9faut<\/p>\n\n\n\n
Neo4J<\/span>.conf  (adaptation \u00e0 notre contexte)<\/p>\n\n\n\n
server.directories.import=import\nserver.bolt.enabled=true\nserver.http.enabled=true\nserver.https.enabled=false\nserver.metrics.csv.rotation.compression=zip\ndb.tx_log.rotation.retention_policy=2 days 2G\nserver.jvm.additional=-XX:+UseG1GC\nserver.jvm.additional=-XX:-OmitStackTraceInFastThrow\nserver.jvm.additional=-XX:+AlwaysPreTouch\nserver.jvm.additional=-XX:+UnlockExperimentalVMOptions\nserver.jvm.additional=-XX:+TrustFinalNonStaticFields\nserver.jvm.additional=-XX:+DisableExplicitGC\nserver.jvm.additional=-XX:-RestrictContended\nserver.jvm.additional=-Djdk.nio.maxCachedBufferSize=1024\nserver.jvm.additional=-Dio.netty.tryReflectionSetAccessible=true\nserver.jvm.additional=-Djdk.tls.ephemeralDHKeySize=2048\nserver.jvm.additional=-Djdk.tls.rejectClientInitiatedRenegotiation=true\nserver.jvm.additional=-XX:FlightRecorderOptions=stackdepth=256\nserver.jvm.additional=-XX:+UnlockDiagnosticVMOptions\nserver.jvm.additional=-XX:+DebugNonSafepoints\nserver.jvm.additional=--add-opens=java.base\/java.nio=ALL-UNNAMED\nserver.jvm.additional=--add-opens=java.base\/java.io=ALL-UNNAMED\nserver.jvm.additional=--add-opens=java.base\/sun.nio.ch=ALL-UNNAMED\nserver.jvm.additional=--enable-native-access=ALL-UNNAMED\nserver.jvm.additional=-Dlog4j2.disable.jmx=true\nserver.windows_service_name=Neo4J<\/span>\nserver.memory.pagecache.size=512M\nserver.default_listen_address=0.0.0.0\nserver.default_advertised_address=192.168.100.221\ndbms.cluster.discovery.v2.endpoints=192.168.100.220:6000,192.168.100.221:6000192.168.100.222:6000\ndbms.cluster.discovery.version=V2_ONLY\ninitial.dbms.default_primaries_count=3\nserver.cluster.advertised_address=192.168.100.221:6000\nserver.cluster.raft.advertised_address=192.168.100.221:7000\nserver.routing.advertised_address=192.168.100.221:7688\nserver.discovery.advertised_address=192.168.100.221:6000\nserver.directories.logs=\/logs<\/code><\/pre>\n\n\n\n
Chargement de la base Neo4J<\/span> pour Emolgine au niveau du cluster \u00e0 l’aide du fichier .dump<\/p>\n\n\n\n
On proc\u00e8de de la m\u00eame fa\u00e7on que sur la version community. Sur chaque n\u0153ud du serveur on ex\u00e9cute la script lance_load.sh qui consiste \u00e0 d\u00e9marrer un conteneur et d’activer Neo4J<\/span>-admin pour charger le fichier Neo4J<\/span>.dump. <\/p>\n\n\n\n
<\/p>\n\n\n\n
V\u00e9rification du fonctionnement<\/p>\n\n\n\n
netstat -a |more et l’utilisation de cypher-shell pour se connecter sur les instances du cluster. <\/p>\n\n\n\n
<\/p>\n