Channels
Server can't be started due to `lost+found` folder
/var/lib/janusgraph
.
Experiencing this issue after restarting the container:
```sh
chown: cannot read directory '/var/lib/janusgraph/lost+found': Permission denied...Phantom Unique Data / Data Too Large?
Could not start BerkeleyJE transaction
JanusGraphManagement from Java client
~20% write performance hit when using custom str IDs?
mergeV()
) nodes to a JanusGraph 1.0.0 instance with a Cassandra+ES backend. Keeping exactly the same client code and test data, I noticed a 20% write slowdown when writing nodes with custom string IDs, rather than custom int IDs. In both cases, the IDs are exactly the same, with the only difference being that in one case I convert int to string, before submitting the query to the JG server (I'm using parametrized scripts submitted via gremlin-python).
Is this a known issue? (I could not find info about this in the documentation)...Mixed Index (ElasticSearch) Backpressure Ignored?
If the primary persistence into the storage backend succeeds but secondary persistence into the indexing backends or the logging system fail, the transaction is still considered to be successful because the storage backend is the authoritative source of the graph. ... In addition, a separate process must be setup that reads the log to identify partially failed transaction and repair any inconsistencies caused....
Could not instantiate implementation: org.janusgraph.diskstorage.es.ElasticSearchIndex
JanusGraph authentication - restricted privileges
Issues faced for consistent indexing (both Composite & Mixed) [ElasticSearch]
Index wasn't created in ElasticSearch, giving a 404, when a vertex totals direct Index Query is performed
--> As a work around. for initial data 1000 Documents of sample data was ingested, and as we expected, the indexes were not present
--> data was re-indexed. Indexes were created in ElasticSearch, and some composite indexes needed re-Indexing as well. After reindexing, the performance was as expected...Custom ID best practice
Indexing
I need to perform upgrade my janusgraph to new version
script in empty-sample.groovy is called twice
JG 0.6 vs JG 1.0 different behaviour for same Gremlin query
ServerGremlinExecutor.<init> - Could not invoke constructor on class org.janusgraph.graphdb.manageme
ConfiguredGraphFactory
for dynamic graph creation.I configured 3 nodes to be the CassandraDB backend cluster, which are all up and running. Here's the complete janusgraph-cql-configuration.properties file:...
many graphs
JanusGraphFactory.open()
any more since JanusGraph Server already opened the graph instances for you.
By using the JanusGraphFactory directly in Gremlin Console you basically circumvent this whole functionality from JanusGraph Server and instead access the JanusGraph API directly to load the graphs yourselves. This means that it doesn't know about your Gremlin Server YAML which also explains why you cannot use graph names defined in that YAML...Indexing on vertex label
Add a collection of values in an edge property
g.addE('link').from('x').to('y').property('p', [1, 2, 4]).next() ...
Custom Vertex IDs and Serialized Graph
g.io("/tmp/foo.kryo").write().iterate()
Then doing the converse with a read()
but then it errors with must provide vertex id
....Concurrent updates during a REINDEX
JanusGraph can begin writing incremental index updates right after an index is defined. However, before the index is complete and usable, JanusGraph must also take a one-time read pass over all existing graph elements associated with the newly indexed schema type(s). Once this reindexing job has completed, the index is fully populated and ready to be used. The index must then be enabled to be used during query processing.which made me wonder how JanusGraph handles incremental updates happening concurrently to a
REINDEX
.
For instance, if we consider a slow reindexing process (e.g. done through the ManagementSystem
interface) that can take several hours, how are concurrent additions/updates/deletions of vertices/edges/properties handled?...