In our AWS Account we have created 3 EC2 instances each with Neo4j Enterprise Causal Cluster AMIs.. We made necessary configurations in the neo4j.template of each Neo4j EC2 Instance to enable Causal Clustering. After making the necessary changes, the system was restarted using the command ./etc/init.d/neo4j start. When checked the status using systemctl status neo4j, it is still neo4j_mode as SINGLE though it was set to CORE. Also the Neo4j UI is not accessible from the browser window.
How can we enable Neo4j Causal Clustering using 3 EC2 Instances with Neo4j AMIs. Is there any specific AMI that we should use with EC2 to enable Causal Clustering. Is there any documentation for the same (EC2 Neo4j Causal Clustering)?
Make sure to read the neo4j configuration section of this page:
Can you please paste a snippet of your neo4j.template file, and your neo4j.conf file, after you start the service?
Below are the configuration changes that we made in the neo4j.template file of one of the EC2 instances.Similar changes were made in the other EC2 instances neo4j.template files. The parameters where Private IPs are used, there we also tried using Public IPs instead of Private IPs.
dbms.security.procedures.unrestricted=apoc.,gds.
Paths of directories in the installation.
dbms.directories.data=/var/lib/neo4j/data
dbms.directories.plugins=/var/lib/neo4j/plugins
dbms.directories.logs=/var/log/neo4j
dbms.directories.lib=/usr/share/neo4j/lib
dbms.directories.run=/var/run/neo4j
#dbms.directories.metrics=/var/lib/neo4j/metrics
#dbms.directories.dumps.root=data/dumps
dbms.directories.import=/var/lib/neo4j/import
dbms.security.auth_enabled=true
#dbms.allow_upgrade=true
#dbms.memory.heap.initial_size=512m
#dbms.memory.heap.max_size=512m
#dbms.memory.pagecache.size=10g
dbms.tx_state.memory_allocation=ON_HEAP
dbms.backup.enabled=$dbms_backup_enabled
dbms.ssl.policy.backup.trust_all=$dbms_ssl_policy_backup_trust_all
dbms.backup.listen_address=0.0.0.0:6364
#*****************************************************************
Network connector configuration
#*****************************************************************
dbms.default_listen_address=0.0.0.0
dbms.default_advertised_address=(PRIVATE IP OF EC2)
Bolt connector
dbms.connector.bolt.enabled=$dbms_connector_bolt_enabled
dbms.connector.bolt.tls_level=$dbms_connector_bolt_tls_level
dbms.connector.bolt.advertised_address=$dbms_connector_bolt_advertised_address
dbms.connector.bolt.listen_address=:7689
HTTP Connector. There must be exactly one HTTP connector.
dbms.connector.http.enabled=$dbms_connector_http_enabled
dbms.connector.http.advertised_address=$dbms_connector_http_advertised_address
dbms.connector.http.listen_address=:7476
HTTPS Connector. There can be zero or one HTTPS connectors.
dbms.connector.https.enabled=$dbms_connector_https_enabled
dbms.connector.https.advertised_address=$dbms_connector_https_advertised_address
dbms.connector.https.listen_address=:6476
dbms.ssl.policy.https.base_directory=$dbms_ssl_policy_https_base_directory
dbms.ssl.policy.https.client_auth=$dbms_ssl_policy_https_client_auth
dbms.ssl.policy.https.trust_all=$dbms_ssl_policy_https_trust_all
#*****************************************************************
Causal Clustering Configuration
#*****************************************************************
causal_clustering.minimum_core_cluster_size_at_formation=3
causal_clustering.minimum_core_cluster_size_at_runtime=3
causal_clustering.initial_discovery_members=(PRIVATE IP OF EC2 SERVER-1):5000,(PRIVATE IP OF EC2 SERVER-2):5001,(PRIVATE IP OF EC2 SERVER-3):5002
causal_clustering.discovery_advertised_address=$causal_clustering_discovery_advertised_address
causal_clustering.discovery_listen_address=:5002
causal_clustering.transaction_listen_address=:6002
causal_clustering.discovery_type=LIST
causal_clustering.raft_listen_address=:7002