Table of Contents | ||||
---|---|---|---|---|
|
...
Pre-requisites
1. Ensure you have the syndeia-cloud-3.
56
_janusgraph_setup.zip
(or latest service pack) downloaded to your home directory (or home directory's Downloads folder) from the download/license instructions sent out by our team.
Note: the .ZIP will pre-create a separate folder for its contents when extracted so there is no need to pre-create a separate folder for it.
2. Ensure you satisfy Janusgraph's pre-requisites, ie: have (Open|Oracle)JDK/JRE + Apache Cassandra (& optionally Elasticsearch) installed. Re. CPU, memory, HD space, etc. this will depend on how much data you expect to store, query, and graph.
3. If using a firewall, and JG will be on a separate server from SC, ensure the following port is accessible (consult your local network admin if required): TCP port 8182 (this is the port to listen to for client connections).
...
Downloading & Extracting JanusGraph
...
3. Unzip Syndeia Cloud's JanusGraph setup package in your home directory ~/
, ie: unzip syndeia-cloud-3.56_janusgraph_setup.zip
-d ~/
...
6. In a new terminal session, cd into the bin dir and run the Syndeia Cloud JanusGraph setup script, ie: cd ~/syndeia-cloud-3.56_janusgraph_setup/bin; ./syndeia-cloud-3.56_janusgraph_setup.bash
.
Panel | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
Note, If you are deploying JG on a multi-node configuration where JG is not on the same machine as Cassandra, please:
|
...
Panel | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This will: - Create/update
- If you installed Elasticsearch on the same machine, add Note: you may be prompted for Avoid all of the following special characters:
|
Tip | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||
When completed, confirm all of the following are true before proceeding or when trying to determine if the JanusGraph service is properly configured and operating. (The tools used and the network locations used are site-dependent.)
|
...
9. To view the logs for JanusGraph, use sudo journalctl -eu janusgraph
& less /opt/janusgraph-0.5.3-full/log/gremlin-server.log
. To follow the log files, you can use sudo journalctl -feu janusgraph
& tail -f /opt/janusgraph-0.5.3-full/log/gremlin-server.log
. You should see output similar to the following (abridged) text:
Note, for your convenience you may wish to create a symlink to /opt/janusgraph-0.5.3-full/log
/
from /var/log
, ie: sudo ln -nfs
/opt/janusgraph-0.5.3-full/log
/ /var/log/janusgraph
...
18. Three things need to occur: you will need to change the Snitch (if not already done for Cassandra), alter the keyspace Replication Factor (RF), and run nodetool repair
on each node (see https://docs.datastax.com/en/archived/cassandra/3.x/cassandra/operations/opsChangeKSStrategy.html for a summary of the process).
- Change the Snitch: see "Switching Snitches": https://docs.datastax.com/en/archived/cassandra/3.x/cassandra/operations/opsChangeKSStrategy.html
Alter the RF: verify the Cassandra “datacenter” name (default =
dc1
) from the CLI by runningnodetool status
and then from Cassandra CQLSH increment the RF for your JanusGraph keyspace(s):Code Block language sql ALTER KEYSPACE syndeia_cloud_auth WITH REPLICATION = { 'class' : 'NetworkTopologyStrategy', '<datacenter_name>' : <total_number_of_nodes> }; -- where <datacenter_name> = the name of the datacenter as shown via nodetool status, and <total_number_of_nodes> = total # of nodes (in the cluster) ALTER KEYSPACE syndeia_cloud_store WITH REPLICATION = { 'class' : 'NetworkTopologyStrategy', '<datacenter_name>' : <total_number_of_nodes> }; -- where <datacenter_name> = the name of the datacenter as shown via nodetool status, and <total_number_of_nodes> = total # of nodes (in the cluster) ALTER KEYSPACE syndeia_cloud_confluence WITH REPLICATION = { 'class' : 'NetworkTopologyStrategy', '<datacenter_name>' : <total_number_of_nodes> }; -- where <datacenter_name> = the name of the datacenter as shown via nodetool status, and <total_number_of_nodes> = total # of nodes (in the cluster) ALTER KEYSPACE syndeia_cloud_graph WITH REPLICATION = { 'class' : 'NetworkTopologyStrategy', '<datacenter_name>' : <total_number_of_nodes> }; -- where <datacenter_name> = the name of the datacenter as shown via nodetool status, and <total_number_of_nodes> = total # of nodes (in the cluster) ALTER KEYSPACE syndeia_cloud_graph_config WITH REPLICATION = { 'class' : 'NetworkTopologyStrategy', '<datacenter_name>' : <total_number_of_nodes> }; -- where <datacenter_name> = the name of the datacenter as shown via nodetool status, and <total_number_of_nodes> = total # of nodes (in the cluster)
Run
nodetool repair
: Runnodetool repair --full
<keyspace_name> on each node (for more details see https://docs.datastax.com/en/dse/5.1/cql/cql/cql_using/cqlUpdateKeyspaceRF.html)
19. Follow "Things to Consider in a Multi-Node JanusGraph Cluster" https://docs.janusgraph.org/0.3.1/things-to-consider-in-a-multi-node-janusgraph-cluster.html
...
Code Block | ||||
---|---|---|---|---|
| ||||
:remote connect tinkerpop.server conf/remote.yaml session :remote console graph = ConfiguredGraphFactory.open('syndeia_cloud_graph'); // should return: ==>standardjanusgraph[cql:[cassandra.mydomain.com]] g = graph.traversal(); g.V(); g.E(); |
The last 2 commands above should not return any results since the graph (syndeia_cloud_graph
) is empty - no vertices or edges.
21.4. Type :quit
Page break macro |
---|
...