|
Re: Confused about GraphSON edges definition
Hi,
I've asked my question over there (here's the thread https://groups.google.com/g/gremlin-users/c/_H3UZyfdvtE) and the possible solution seems to be to use readVertices() instead of read() or
Hi,
I've asked my question over there (here's the thread https://groups.google.com/g/gremlin-users/c/_H3UZyfdvtE) and the possible solution seems to be to use readVertices() instead of read() or
|
By
Laura Morales <lauretas@...>
·
#6138
·
|
|
Re: Removing a vertex is not removing recently added properties in different transaction
Please find my answers inline:
do you use CompositeIndex or MixedIndex?
- i am suing composite index
is it certain that the two transaction do not overlap in time (as "next" suggests)?
- They do not
Please find my answers inline:
do you use CompositeIndex or MixedIndex?
- i am suing composite index
is it certain that the two transaction do not overlap in time (as "next" suggests)?
- They do not
|
By
Priyanka Jindal
·
#6137
·
|
|
Re: Confused about GraphSON edges definition
Hi Laura,
If you want to know, you would better ask on the TinkerPop users list. Note that graphSON is not designed as a human-readable or standardized interchange format, but rather as interchange
Hi Laura,
If you want to know, you would better ask on the TinkerPop users list. Note that graphSON is not designed as a human-readable or standardized interchange format, but rather as interchange
|
By
hadoopmarc@...
·
#6136
·
|
|
Re: CQL scaling limit?
Nice work!
By
hadoopmarc@...
·
#6135
·
|
|
Confused about GraphSON edges definition
I'm looking at this example from TinkerPop
I'm looking at this example from TinkerPop
|
By
Laura Morales <lauretas@...>
·
#6134
·
|
|
Re: Removing a vertex is not removing recently added properties in different transaction
The behavior you describe sounds like the behavior one experiences for transactions occurring in parallel. So let us investigate some further:
do you use CompositeIndex or MixedIndex?
is it certain
The behavior you describe sounds like the behavior one experiences for transactions occurring in parallel. So let us investigate some further:
do you use CompositeIndex or MixedIndex?
is it certain
|
By
hadoopmarc@...
·
#6133
·
|
|
Re: Index stuck on INSTALLED (single instance of JanusGraph)
It still does not work for me.
It still does not work for me.
|
By
fredrick.eisele@...
·
#6132
·
|
|
Re: CQL scaling limit?
Hi Marc,
I tried rerunning the scaling test on a fresh graph with ids.block-size=10000000 , unfortunately I haven't seen any performance gain.
I also tried ids.block-size=10000000 and
Hi Marc,
I tried rerunning the scaling test on a fresh graph with ids.block-size=10000000 , unfortunately I haven't seen any performance gain.
I also tried ids.block-size=10000000 and
|
By
madams@...
·
#6131
·
|
|
Removing a vertex is not removing recently added properties in different transaction
I am using janus client with hbase as storage backend.
In my case, I am using index ind1 to fetch vertices from the graph. Upon fetching I am adding some properties (e.g one such property is p1) to
I am using janus client with hbase as storage backend.
In my case, I am using index ind1 to fetch vertices from the graph. Upon fetching I am adding some properties (e.g one such property is p1) to
|
By
Priyanka Jindal
·
#6130
·
|
|
TTL for write-ahead logs not working
Hi,
I enabled write-ahead logs to support index recovery for secondary persistence failures. I am trying to set TTL for write-ahead logs through JanusGraphManagement setting "log.tx.ttl".
Tried below
Hi,
I enabled write-ahead logs to support index recovery for secondary persistence failures. I am trying to set TTL for write-ahead logs through JanusGraphManagement setting "log.tx.ttl".
Tried below
|
By
Radhika Kundam
·
#6129
·
|
|
Re: Not able to enable Write-ahead logs using tx.log-tx for existing JanusGraph setup
Thank you Boxuan for the confirmation. I used the same approach of reopening graph as of now.
It would be good if "logTransactions" can be refreshed on update of tx.log-tx by providing setter method
Thank you Boxuan for the confirmation. I used the same approach of reopening graph as of now.
It would be good if "logTransactions" can be refreshed on update of tx.log-tx by providing setter method
|
By
Radhika Kundam
·
#6128
·
|
|
Re: Too low Performance when running PageRank and WCC on Graph500
Well, the spec I am using is 32vCPU and 128GB memory. But I am testing Janusgraph with Cassandra as storage backend.
I think this is not a thing with memory spec. I think maybe it is a thing with
Well, the spec I am using is 32vCPU and 128GB memory. But I am testing Janusgraph with Cassandra as storage backend.
I think this is not a thing with memory spec. I think maybe it is a thing with
|
By
shepherdkingqsp@...
·
#6127
·
|
|
Re: Not able to enable Write-ahead logs using tx.log-tx for existing JanusGraph setup
Hi Radhika,
Got it. You are right, you need to reopen the graph after setting `tx.log-tx`.
Hi Radhika,
Got it. You are right, you need to reopen the graph after setting `tx.log-tx`.
|
By
Boxuan Li
·
#6126
·
|
|
Re: multilevel properties depth
Hi Laura,
You can only add a single level of metaproperties. One can understand this from the java docs.In a TinkerGraph a regular property is a TinkerVertexProperty with a property() method to add
Hi Laura,
You can only add a single level of metaproperties. One can understand this from the java docs.In a TinkerGraph a regular property is a TinkerVertexProperty with a property() method to add
|
By
hadoopmarc@...
·
#6125
·
|
|
Re: graphml properties of properties
Hi Laura,
Using TinkerGraph I exported a graph to graphSON in the way shown above. I reloaded it as follows:So, the metaproperty added s read from graphSON. Do you mean to say that you cannot do the
Hi Laura,
Using TinkerGraph I exported a graph to graphSON in the way shown above. I reloaded it as follows:So, the metaproperty added s read from graphSON. Do you mean to say that you cannot do the
|
By
hadoopmarc@...
·
#6124
·
|
|
Re: Too low Performance when running PageRank and WCC on Graph500
Hi Shipeng,
Did you use their machine specs: 32 vCPU and 244 GB memory? The graph is pretty big for in-memory use during OLAP:
Best wishes, Marc
Hi Shipeng,
Did you use their machine specs: 32 vCPU and 244 GB memory? The graph is pretty big for in-memory use during OLAP:
Best wishes, Marc
|
By
hadoopmarc@...
·
#6123
·
|
|
Re: CQL scaling limit?
Just one more thing to rule out: did you set cpu.request and cpu.limit of the indexer containers to the same value? You want the pods to be really independent for this test.
Just one more thing to rule out: did you set cpu.request and cpu.limit of the indexer containers to the same value? You want the pods to be really independent for this test.
|
By
hadoopmarc@...
·
#6122
·
|
|
multilevel properties depth
How many "levels" of multilevel properties are supported by Janus? What I mean is, can I only add properties about other properties, or can I add an arbitrary number of multilevel properties, that is
How many "levels" of multilevel properties are supported by Janus? What I mean is, can I only add properties about other properties, or can I add an arbitrary number of multilevel properties, that is
|
By
Laura Morales <lauretas@...>
·
#6121
·
|
|
Re: CQL scaling limit?
Hi Marc,
If you know how to handle MetricManager, that sounds fine. I was thinking in more basic terms: adding some log statements to you indexer java code.
Regarding the id block allocation, some
Hi Marc,
If you know how to handle MetricManager, that sounds fine. I was thinking in more basic terms: adding some log statements to you indexer java code.
Regarding the id block allocation, some
|
By
hadoopmarc@...
·
#6120
·
|
|
Re: CQL scaling limit?
Hi Marc,
We're running on Kubernetes, and there's no cpu limitations on the indexer.
Thanks for pointing this out, I actually haven't checked the overall resources of the cluster... It's a good
Hi Marc,
We're running on Kubernetes, and there's no cpu limitations on the indexer.
Thanks for pointing this out, I actually haven't checked the overall resources of the cluster... It's a good
|
By
madams@...
·
#6119
·
|