1. janusgraph-users@lists.lfaidata.foundation
  2. Messages
   Date   
Can someone help us to know how to explore janusgraph database functions ?

DRAY <ani...@...>
 

Can someone help us to know how to explore janusgraph database functions used in Gremlin language and also best approach to start using and understanding janusgraph  ( to create own graph data having vertexs and edges with the commands to understand better and to explore further )

We wanted to use graph database and its features in our Company and has been assigned a project to explore graph database and specially janusgraph -  we are going through the janusgraph website but couldn't get detail info on janusgraph functions and its usage and also to create own graph data. 

So our request is to please help us on the same to explore janusgraph.

Thank you in Advance, Appreciate your support.
Best (Correct?) Way to Access JanusGraph Remotely

zbec...@...
 

Hello, I am in the process of building a Java, RPC server that takes in multi-threaded requests, queries the database and returns a result to the client. I understand JanusGraph allows concurrent transactions and I would prefer all requests run within their own transaction. However, I am a bit confused as to access JanusGraph remotely as I have seen multiple implementations.

The first uses:
JanusGraph graph = JanusGraphFactory.build()
      .set("storage.backend", "hbase")
      .set("storage.hostname", "lily.local")
      .set("storage.hbase.table", "birdr")
      .open();

GraphTraversalSource g = graph.traversal();

Then I would call the following in each request block of the RPC server:
g.tx().createThreadedTx()


But this appears to building a JanusGraph server. Is that correct?

Another implementation I have seen is:

Cluster.open('path to config file');

And then I would call the following in each request block of the RPC server:

Client client = cluster.connect();
GraphTraversalSource g = AnonymousTraversalSource.traversal().withRemote(DriverRemoteConnection.using(client, "g"));

Then simply close the client at the end of each request. However this GraphTraversalSource does not support transactions,

I believe the second option is more correct, but do Client instances maintain transactions? Are they transactions themselves?

Any kind of explanation or clarity would be greatly appreciated.
Getting RowTooBigException while firing janus query backed by hbase

Priyanka Jindal <priyanka...@...>
 

Hi 

In my case janusgraph storage is backed by hbase and i am firing the following query:

query = tx.query().has("key1","v1").has("key2","v2").limit(FIXED_VALUE)
for(T element : query.properties()){

}

It contains the composite index. vertex is not partitioned.

So now while calling query.properties() it fails with "org.apache.hadoop.hbase.regionserver.RowTooBigException: org.apache.hadoop.hbase.regionserver.RowTooBigException: Max row size allowed: 1073741824, but the row is bigger than that." exception from hbase side.

As per my understanding, the reason for this is : the row which is getting fetched from hbase is greater than the threshold value set by hbase. And a row corresponds to the edges and properties of single vertex.

So my question is:
1. When the above query is invoked, how exactly it works? Does it try to fetch all the vertices and then filter depending on passed key value pairs?
2. I have tried increasing value of threshold value of hbase, but even then getting the same error. What could be the reason for that
Re: Adding this property for key [~T$SchemaName] and value [...] violates a uniqueness constraint

BO XUAN LI <libo...@...>
 

Correct. See https://docs.janusgraph.org/basics/schema/#relation-types

On Aug 11, 2020, at 1:03 AM, Matteo Lissandrini <matteo.l...@...> wrote:

So there is no way to have a graph with a property name and an edge label with the same name?

On Monday, 10 August 2020 at 18:28:48 UTC+2 libo...@connect.hku.hk wrote:
Yeah, that's possible. You need to make sure properties and labels don't have the same name.
On Tuesday, August 11, 2020 at 12:25:46 AM UTC+8 Matteo Lissandrini wrote:
I am loading a graph from scratch in an empty database.
Could it be that there may be an edge label and a property name with the same name?


On Monday, 10 August 2020 at 18:21:36 UTC+2 li...@... wrote:
Are you running the code against a clean database? Does the property already exist before you run this piece of code?

On Aug 11, 2020, at 12:14 AM, Matteo Lissandrini <matt...@...> wrote:

Hi Boxuan,
thanks for the reply.

This is the full error:

org.janusgraph.core.SchemaViolationException: Adding this property for key [~T$SchemaName] and value [rtns8_designation] violates a uniqueness constraint [SystemIndex#~T$SchemaName]

I actually run a distinct before creating the schema
here is the relevant piece of code

So I am quite sure I am not creating it twice. Any ideas?

Thanks,
Matteo





On Sunday, 9 August 2020 at 04:57:43 UTC+2 libo...@connect.hku.hk wrote:
Hi Matteo,

The error log is indeed a bit counter-intuitive. Looks like your program was trying to create a new property (or label), but the property (or label) already existed in the database.

You may want to check your program. I would suggest checking the existence of property (label) before trying to create one.

Regards,
Boxuan
On Friday, August 7, 2020 at 11:21:07 PM UTC+8 Matteo Lissandrini wrote:
Hello,

I'm having this error thrown at me during loading of a large graph (dbpedia)
and I cannot understand what is it complaining about.

Can you help me?

Thanks,
Matteo

-- 
You received this message because you are subscribed to the Google Groups "JanusGraph users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgr...@....
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-users/87e2ab14-63d5-4e3d-afa5-a020adad8dfan%40googlegroups.com.


-- 
You received this message because you are subscribed to the Google Groups "JanusGraph users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgra...@....
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-users/3fc2b92b-936c-4a2c-bec0-c6134a749370n%40googlegroups.com.
Re: Adding this property for key [~T$SchemaName] and value [...] violates a uniqueness constraint

Matteo Lissandrini <matteo.l...@...>
 

So there is no way to have a graph with a property name and an edge label with the same name?


On Monday, 10 August 2020 at 18:28:48 UTC+2 li...@... wrote:
Yeah, that's possible. You need to make sure properties and labels don't have the same name.
On Tuesday, August 11, 2020 at 12:25:46 AM UTC+8 Matteo Lissandrini wrote:
I am loading a graph from scratch in an empty database.
Could it be that there may be an edge label and a property name with the same name?


On Monday, 10 August 2020 at 18:21:36 UTC+2 li...@... wrote:
Are you running the code against a clean database? Does the property already exist before you run this piece of code?

On Aug 11, 2020, at 12:14 AM, Matteo Lissandrini <matt...@...> wrote:

Hi Boxuan,
thanks for the reply.

This is the full error:

org.janusgraph.core.SchemaViolationException: Adding this property for key [~T$SchemaName] and value [rtns8_designation] violates a uniqueness constraint [SystemIndex#~T$SchemaName]

I actually run a distinct before creating the schema
here is the relevant piece of code

So I am quite sure I am not creating it twice. Any ideas?

Thanks,
Matteo





On Sunday, 9 August 2020 at 04:57:43 UTC+2 libo...@connect.hku.hk wrote:
Hi Matteo,

The error log is indeed a bit counter-intuitive. Looks like your program was trying to create a new property (or label), but the property (or label) already existed in the database.

You may want to check your program. I would suggest checking the existence of property (label) before trying to create one.

Regards,
Boxuan
On Friday, August 7, 2020 at 11:21:07 PM UTC+8 Matteo Lissandrini wrote:
Hello,

I'm having this error thrown at me during loading of a large graph (dbpedia)
and I cannot understand what is it complaining about.

Can you help me?

Thanks,
Matteo

-- 
You received this message because you are subscribed to the Google Groups "JanusGraph users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgr...@....
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-users/87e2ab14-63d5-4e3d-afa5-a020adad8dfan%40googlegroups.com.
Re: Adding this property for key [~T$SchemaName] and value [...] violates a uniqueness constraint

Boxuan Li <libo...@...>
 

Yeah, that's possible. You need to make sure properties and labels don't have the same name.
On Tuesday, August 11, 2020 at 12:25:46 AM UTC+8 Matteo Lissandrini wrote:

I am loading a graph from scratch in an empty database.
Could it be that there may be an edge label and a property name with the same name?


On Monday, 10 August 2020 at 18:21:36 UTC+2 li...@... wrote:
Are you running the code against a clean database? Does the property already exist before you run this piece of code?

On Aug 11, 2020, at 12:14 AM, Matteo Lissandrini <matt...@...> wrote:

Hi Boxuan,
thanks for the reply.

This is the full error:

org.janusgraph.core.SchemaViolationException: Adding this property for key [~T$SchemaName] and value [rtns8_designation] violates a uniqueness constraint [SystemIndex#~T$SchemaName]

I actually run a distinct before creating the schema
here is the relevant piece of code

So I am quite sure I am not creating it twice. Any ideas?

Thanks,
Matteo





On Sunday, 9 August 2020 at 04:57:43 UTC+2 libo...@connect.hku.hk wrote:
Hi Matteo,

The error log is indeed a bit counter-intuitive. Looks like your program was trying to create a new property (or label), but the property (or label) already existed in the database.

You may want to check your program. I would suggest checking the existence of property (label) before trying to create one.

Regards,
Boxuan
On Friday, August 7, 2020 at 11:21:07 PM UTC+8 Matteo Lissandrini wrote:
Hello,

I'm having this error thrown at me during loading of a large graph (dbpedia)
and I cannot understand what is it complaining about.

Can you help me?

Thanks,
Matteo

-- 
You received this message because you are subscribed to the Google Groups "JanusGraph users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgr...@....
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-users/87e2ab14-63d5-4e3d-afa5-a020adad8dfan%40googlegroups.com.
Re: Adding this property for key [~T$SchemaName] and value [...] violates a uniqueness constraint

Matteo Lissandrini <matteo.l...@...>
 

I am loading a graph from scratch in an empty database.
Could it be that there may be an edge label and a property name with the same name?


On Monday, 10 August 2020 at 18:21:36 UTC+2 li...@... wrote:
Are you running the code against a clean database? Does the property already exist before you run this piece of code?

On Aug 11, 2020, at 12:14 AM, Matteo Lissandrini <matt...@...> wrote:

Hi Boxuan,
thanks for the reply.

This is the full error:

org.janusgraph.core.SchemaViolationException: Adding this property for key [~T$SchemaName] and value [rtns8_designation] violates a uniqueness constraint [SystemIndex#~T$SchemaName]

I actually run a distinct before creating the schema
here is the relevant piece of code

So I am quite sure I am not creating it twice. Any ideas?

Thanks,
Matteo





On Sunday, 9 August 2020 at 04:57:43 UTC+2 libo...@connect.hku.hk wrote:
Hi Matteo,

The error log is indeed a bit counter-intuitive. Looks like your program was trying to create a new property (or label), but the property (or label) already existed in the database.

You may want to check your program. I would suggest checking the existence of property (label) before trying to create one.

Regards,
Boxuan
On Friday, August 7, 2020 at 11:21:07 PM UTC+8 Matteo Lissandrini wrote:
Hello,

I'm having this error thrown at me during loading of a large graph (dbpedia)
and I cannot understand what is it complaining about.

Can you help me?

Thanks,
Matteo

-- 
You received this message because you are subscribed to the Google Groups "JanusGraph users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgr...@....
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-users/87e2ab14-63d5-4e3d-afa5-a020adad8dfan%40googlegroups.com.
Re: Adding this property for key [~T$SchemaName] and value [...] violates a uniqueness constraint

BO XUAN LI <libo...@...>
 

Are you running the code against a clean database? Does the property already exist before you run this piece of code?

On Aug 11, 2020, at 12:14 AM, Matteo Lissandrini <matteo.l...@...> wrote:

Hi Boxuan,
thanks for the reply.

This is the full error:

org.janusgraph.core.SchemaViolationException: Adding this property for key [~T$SchemaName] and value [rtns8_designation] violates a uniqueness constraint [SystemIndex#~T$SchemaName]

I actually run a distinct before creating the schema
here is the relevant piece of code

So I am quite sure I am not creating it twice. Any ideas?

Thanks,
Matteo





On Sunday, 9 August 2020 at 04:57:43 UTC+2 libo...@connect.hku.hk wrote:
Hi Matteo,

The error log is indeed a bit counter-intuitive. Looks like your program was trying to create a new property (or label), but the property (or label) already existed in the database.

You may want to check your program. I would suggest checking the existence of property (label) before trying to create one.

Regards,
Boxuan
On Friday, August 7, 2020 at 11:21:07 PM UTC+8 Matteo Lissandrini wrote:
Hello,

I'm having this error thrown at me during loading of a large graph (dbpedia)
and I cannot understand what is it complaining about.

Can you help me?

Thanks,
Matteo

-- 
You received this message because you are subscribed to the Google Groups "JanusGraph users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgra...@....
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-users/87e2ab14-63d5-4e3d-afa5-a020adad8dfan%40googlegroups.com.
Re: Adding this property for key [~T$SchemaName] and value [...] violates a uniqueness constraint

Matteo Lissandrini <matteo.l...@...>
 

Hi Boxuan,
thanks for the reply.

This is the full error:

org.janusgraph.core.SchemaViolationException: Adding this property for key [~T$SchemaName] and value [rtns8_designation] violates a uniqueness constraint [SystemIndex#~T$SchemaName]

I actually run a distinct before creating the schema
here is the relevant piece of code
https://pastebin.com/BaYc5ej5

So I am quite sure I am not creating it twice. Any ideas?

Thanks,
Matteo





On Sunday, 9 August 2020 at 04:57:43 UTC+2 li...@... wrote:
Hi Matteo,

The error log is indeed a bit counter-intuitive. Looks like your program was trying to create a new property (or label), but the property (or label) already existed in the database.

You may want to check your program. I would suggest checking the existence of property (label) before trying to create one.

Regards,
Boxuan
On Friday, August 7, 2020 at 11:21:07 PM UTC+8 Matteo Lissandrini wrote:
Hello,

I'm having this error thrown at me during loading of a large graph (dbpedia)
and I cannot understand what is it complaining about.

Can you help me?

Thanks,
Matteo
Re: Index on subquery not working

Veerle <vvanbe...@...>
 

Thanks for the answer but putting  has(“property”, true) before both(“connected”) changes the results of the query.

I actually simplefied my query a bit for my question here but what I want is a query that selects all relations where on one side the property is true and on the other side the property is false.
Something like this:

V()
        .hasLabel("road")
        .has("property", true)
        .both("connected")
        .hasLabel("road")
        .has("property", false)
.next()

The first part of the query uses the index, but the second part isn't.

Thanks, Veerle
Re: Index on subquery not working

BO XUAN LI <libo...@...>
 

Hi Veerle,

Try putting both(“connected”) after has(“property”, true).

Regards,
Boxuan

On Aug 10, 2020, at 8:10 PM, Veerle <vvanbe...@...> wrote:

Hi,

I do have a graph with about 1 million vertexes and a many to many relation between those vertexes.
The vertexes are 

I created a mixed index 

management.buildIndex(indexName, Vertex.class)
                .addKey(management.getPropertyKey("property"))
                .indexOnly(road)
                .buildMixedIndex("search"); 

The index is working correctly, I can see it popping up in the profile output:
graph
        .V()
        .hasLabel("road")
        .has("property", true)
        .profile().next()

But when I want to have the same on the other side of the "connected" relation, the index is not used anymore.
graph
        .V().both("connected")
        .hasLabel("road")
        .has("property", true)
        .profile().next()
        
Does someone know how I get the subquery to use the index?

Thanks a lot, Veerle

--
You received this message because you are subscribed to the Google Groups "JanusGraph users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgra...@....
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-users/a9e313d7-cffa-442a-b2ca-f20339767103o%40googlegroups.com.
Index on subquery not working

Veerle <vvanbe...@...>
 

Hi,

I do have a graph with about 1 million vertexes and a many to many relation between those vertexes.
The vertexes are 

I created a mixed index 

management.buildIndex(indexName, Vertex.class)
                .addKey(management.getPropertyKey("property"))
                .indexOnly(road)
                .buildMixedIndex("search"); 

The index is working correctly, I can see it popping up in the profile output:
graph
        .V()
        .hasLabel("road")
        .has("property", true)
        .profile().next()

But when I want to have the same on the other side of the "connected" relation, the index is not used anymore.
graph
        .V().both("connected")
        .hasLabel("road")
        .has("property", true)
        .profile().next()
        
Does someone know how I get the subquery to use the index?

Thanks a lot, Veerle
Re: HA about janusGraph

Vayne Yang <vayne...@...>
 

Hi Marc,
  
  I see, Thank you so much!

On Monday, August 10, 2020 at 5:21:38 PM UTC+8, HadoopMarc wrote:
Hi Vayne Yang,

Query failing to a DOWN node because of a wrong node selection seems unlikely because JanusGraph uses the regular cassandra/cql drivers.

The similar thread below suggests to look into the gremlin-server logs for QUORUM warnings and to also configure the replication-factor on the janusgraph side.

HTH,    Marc

Op maandag 10 augustus 2020 om 10:44:00 UTC+2 schreef Vayne Yang:
Hi Marc,

  One more question please! When a query is sent to gremlin-server, what will the gremlin-server do with the storage backend? Is there any possible that the query is sent to a DOWN cassandra node which cause the query failed?

  Best wishes!


On Monday, August 10, 2020 at 2:43:00 PM UTC+8, HadoopMarc wrote:
Hi Vayne Yang,

Can you eleborate on "the query may be failed"? Is it just a warning followed by an automatic new attempt or does the query produce no result? Can you add the stacktrace?

Best wishes,    Marc

Op maandag 10 augustus 2020 om 08:13:41 UTC+2 schreef Vayne Yang:
hi Marc!
  Thanks for your reply!
  I am pretty sure the spaces are not the problems. e.g. https://docs.janusgraph.org/basics/example-config/#cassandra-remote configured in the same way. And after open the configure file with JanusGraphFactory, gremlin console also print 'standardjanusgraph[cql:[172.1.1.1, 172.1.1.2, 172.1.1.3, 172.1.1.4]]'.
  

On Monday, August 10, 2020 at 1:34:01 PM UTC+8, HadoopMarc wrote:
Hi Vayne Yang,
I am not sure this is the problem, but the spaces in your storage.hostname string look suspect.

HTH,    Marc

Op maandag 10 augustus 2020 om 04:57:33 UTC+2 schreef Vayne Yang:
Hi JanusGraph users,

    If I have a cassandra cluster with 4 machines, what should I configure the  'storage.hostname' as to make the most HA?

    This is my configuration now:  storage.hostname = 172.1.1.1, 172.1.1.2, 172.1.1.3, 172.1.1.4, but once A cassandra node is DOWN, the query to gremlin-server may be failed.

    Thank you for any hint and response!
Re: HA about janusGraph

HadoopMarc <bi...@...>
 

Hi Vayne Yang,

Query failing to a DOWN node because of a wrong node selection seems unlikely because JanusGraph uses the regular cassandra/cql drivers.

The similar thread below suggests to look into the gremlin-server logs for QUORUM warnings and to also configure the replication-factor on the janusgraph side.

HTH,    Marc

Op maandag 10 augustus 2020 om 10:44:00 UTC+2 schreef Vayne Yang:

Hi Marc,

  One more question please! When a query is sent to gremlin-server, what will the gremlin-server do with the storage backend? Is there any possible that the query is sent to a DOWN cassandra node which cause the query failed?

  Best wishes!


On Monday, August 10, 2020 at 2:43:00 PM UTC+8, HadoopMarc wrote:
Hi Vayne Yang,

Can you eleborate on "the query may be failed"? Is it just a warning followed by an automatic new attempt or does the query produce no result? Can you add the stacktrace?

Best wishes,    Marc

Op maandag 10 augustus 2020 om 08:13:41 UTC+2 schreef Vayne Yang:
hi Marc!
  Thanks for your reply!
  I am pretty sure the spaces are not the problems. e.g. https://docs.janusgraph.org/basics/example-config/#cassandra-remote configured in the same way. And after open the configure file with JanusGraphFactory, gremlin console also print 'standardjanusgraph[cql:[172.1.1.1, 172.1.1.2, 172.1.1.3, 172.1.1.4]]'.
  

On Monday, August 10, 2020 at 1:34:01 PM UTC+8, HadoopMarc wrote:
Hi Vayne Yang,
I am not sure this is the problem, but the spaces in your storage.hostname string look suspect.

HTH,    Marc

Op maandag 10 augustus 2020 om 04:57:33 UTC+2 schreef Vayne Yang:
Hi JanusGraph users,

    If I have a cassandra cluster with 4 machines, what should I configure the  'storage.hostname' as to make the most HA?

    This is my configuration now:  storage.hostname = 172.1.1.1, 172.1.1.2, 172.1.1.3, 172.1.1.4, but once A cassandra node is DOWN, the query to gremlin-server may be failed.

    Thank you for any hint and response!
Re: HA about janusGraph

Vayne Yang <vayne...@...>
 

Hi Marc,

  One more question please! When a query is sent to gremlin-server, what will the gremlin-server do with the storage backend? Is there any possible that the query is sent to a DOWN cassandra node which cause the query failed?

  Best wishes!


On Monday, August 10, 2020 at 2:43:00 PM UTC+8, HadoopMarc wrote:
Hi Vayne Yang,

Can you eleborate on "the query may be failed"? Is it just a warning followed by an automatic new attempt or does the query produce no result? Can you add the stacktrace?

Best wishes,    Marc

Op maandag 10 augustus 2020 om 08:13:41 UTC+2 schreef Vayne Yang:
hi Marc!
  Thanks for your reply!
  I am pretty sure the spaces are not the problems. e.g. https://docs.janusgraph.org/basics/example-config/#cassandra-remote configured in the same way. And after open the configure file with JanusGraphFactory, gremlin console also print 'standardjanusgraph[cql:[172.1.1.1, 172.1.1.2, 172.1.1.3, 172.1.1.4]]'.
  

On Monday, August 10, 2020 at 1:34:01 PM UTC+8, HadoopMarc wrote:
Hi Vayne Yang,
I am not sure this is the problem, but the spaces in your storage.hostname string look suspect.

HTH,    Marc

Op maandag 10 augustus 2020 om 04:57:33 UTC+2 schreef Vayne Yang:
Hi JanusGraph users,

    If I have a cassandra cluster with 4 machines, what should I configure the  'storage.hostname' as to make the most HA?

    This is my configuration now:  storage.hostname = 172.1.1.1, 172.1.1.2, 172.1.1.3, 172.1.1.4, but once A cassandra node is DOWN, the query to gremlin-server may be failed.

    Thank you for any hint and response!
Re: HA about janusGraph

Vayne Yang <vayne...@...>
 

Hi Marc,
  Is that means, JanusGraph itself is HA right? If so, maybe the problem is that read-consistency-level=QUORUM  is too strict.
  Sorry I can't repeat the error immediately. if I run into this problem again, I will report here.
  Thanks for your help !


On Monday, August 10, 2020 at 2:43:00 PM UTC+8, HadoopMarc wrote:
Hi Vayne Yang,

Can you eleborate on "the query may be failed"? Is it just a warning followed by an automatic new attempt or does the query produce no result? Can you add the stacktrace?

Best wishes,    Marc

Op maandag 10 augustus 2020 om 08:13:41 UTC+2 schreef Vayne Yang:
hi Marc!
  Thanks for your reply!
  I am pretty sure the spaces are not the problems. e.g. https://docs.janusgraph.org/basics/example-config/#cassandra-remote configured in the same way. And after open the configure file with JanusGraphFactory, gremlin console also print 'standardjanusgraph[cql:[172.1.1.1, 172.1.1.2, 172.1.1.3, 172.1.1.4]]'.
  

On Monday, August 10, 2020 at 1:34:01 PM UTC+8, HadoopMarc wrote:
Hi Vayne Yang,
I am not sure this is the problem, but the spaces in your storage.hostname string look suspect.

HTH,    Marc

Op maandag 10 augustus 2020 om 04:57:33 UTC+2 schreef Vayne Yang:
Hi JanusGraph users,

    If I have a cassandra cluster with 4 machines, what should I configure the  'storage.hostname' as to make the most HA?

    This is my configuration now:  storage.hostname = 172.1.1.1, 172.1.1.2, 172.1.1.3, 172.1.1.4, but once A cassandra node is DOWN, the query to gremlin-server may be failed.

    Thank you for any hint and response!
add SINGLE type edge for two partitioned vertex can not duplicate removal

Moon Hu <199512...@...>
 

- Janusgraph Version: 0.0.3
- Storage Backend: hbase 1.2.6
- Mixed Index Backend:elasticsearch 6.3.0

I have two partitioned vertex ,vertex id is 57402 and 30245090, and i defined a SIMPLE  type edge named 'father', i add this relation for the vterices ten times, i can query ten relations from graph
Re: HA about janusGraph

HadoopMarc <bi...@...>
 

Hi Vayne Yang,

Can you eleborate on "the query may be failed"? Is it just a warning followed by an automatic new attempt or does the query produce no result? Can you add the stacktrace?

Best wishes,    Marc

Op maandag 10 augustus 2020 om 08:13:41 UTC+2 schreef Vayne Yang:

hi Marc!
  Thanks for your reply!
  I am pretty sure the spaces are not the problems. e.g. https://docs.janusgraph.org/basics/example-config/#cassandra-remote configured in the same way. And after open the configure file with JanusGraphFactory, gremlin console also print 'standardjanusgraph[cql:[172.1.1.1, 172.1.1.2, 172.1.1.3, 172.1.1.4]]'.
  

On Monday, August 10, 2020 at 1:34:01 PM UTC+8, HadoopMarc wrote:
Hi Vayne Yang,
I am not sure this is the problem, but the spaces in your storage.hostname string look suspect.

HTH,    Marc

Op maandag 10 augustus 2020 om 04:57:33 UTC+2 schreef Vayne Yang:
Hi JanusGraph users,

    If I have a cassandra cluster with 4 machines, what should I configure the  'storage.hostname' as to make the most HA?

    This is my configuration now:  storage.hostname = 172.1.1.1, 172.1.1.2, 172.1.1.3, 172.1.1.4, but once A cassandra node is DOWN, the query to gremlin-server may be failed.

    Thank you for any hint and response!
Re: HA about janusGraph

Vayne Yang <vayne...@...>
 

hi Marc!
  Thanks for your reply!
  I am pretty sure the spaces are not the problems. e.g. https://docs.janusgraph.org/basics/example-config/#cassandra-remote configured in the same way. And after open the configure file with JanusGraphFactory, gremlin console also print 'standardjanusgraph[cql:[172.1.1.1, 172.1.1.2, 172.1.1.3, 172.1.1.4]]'.
  


On Monday, August 10, 2020 at 1:34:01 PM UTC+8, HadoopMarc wrote:
Hi Vayne Yang,
I am not sure this is the problem, but the spaces in your storage.hostname string look suspect.

HTH,    Marc

Op maandag 10 augustus 2020 om 04:57:33 UTC+2 schreef Vayne Yang:
Hi JanusGraph users,

    If I have a cassandra cluster with 4 machines, what should I configure the  'storage.hostname' as to make the most HA?

    This is my configuration now:  storage.hostname = 172.1.1.1, 172.1.1.2, 172.1.1.3, 172.1.1.4, but once A cassandra node is DOWN, the query to gremlin-server may be failed.

    Thank you for any hint and response!
Re: Can't add a vertex with long property value - ERROR Connection reset by peer

Kenn Falcon <kennf...@...>
 

Thx

在2020年8月6日星期四 UTC+8 下午9:56:51<HadoopMarc> 写道：

You will also have to configure the maximum websockets content length at the driver side, see:


Best wishes,    Marc

Op donderdag 6 augustus 2020 om 15:34:12 UTC+2 schreef ke...@...:
When I add vertices (some property value length is very long) with java remote api, The client got a Exception:

ava.util.concurrent.CompletionException: java.io.IOException: Connection reset by peer
at java.util.concurrent.CompletableFuture.reportJoin(CompletableFuture.java:375)
at java.util.concurrent.CompletableFuture.join(CompletableFuture.java:1947)
at org.apache.tinkerpop.gremlin.driver.ResultSet.one(ResultSet.java:119)
at org.apache.tinkerpop.gremlin.driver.ResultSet$1.hasNext(ResultSet.java:171)
at org.apache.tinkerpop.gremlin.driver.ResultSet$1.next(ResultSet.java:178)
at org.apache.tinkerpop.gremlin.driver.ResultSet$1.next(ResultSet.java:165)
at org.apache.tinkerpop.gremlin.driver.remote.DriverRemoteTraversal$TraverserIterator.next(DriverRemoteTraversal.java:146)
at org.apache.tinkerpop.gremlin.driver.remote.DriverRemoteTraversal$TraverserIterator.next(DriverRemoteTraversal.java:131)
at org.apache.tinkerpop.gremlin.driver.remote.DriverRemoteTraversal.nextTraverser(DriverRemoteTraversal.java:112)
at org.apache.tinkerpop.gremlin.process.remote.traversal.step.map.RemoteStep.processNextStart(RemoteStep.java:80)
at org.apache.tinkerpop.gremlin.process.traversal.step.util.AbstractStep.next(AbstractStep.java:128)
at org.apache.tinkerpop.gremlin.process.traversal.step.util.AbstractStep.next(AbstractStep.java:38)
at org.apache.tinkerpop.gremlin.process.traversal.util.DefaultTraversal.next(DefaultTraversal.java:205)
at com.shuwen.janusgraph.processor.core.GraphProcessor.create(GraphProcessor.java:242)
at com.shuwen.janusgraph.processor.core.GraphProcessor.process(GraphProcessor.java:109)
at com.shuwen.janusgraph.processor.core.GraphProcessor.process(GraphProcessor.java:58)
at com.alicloud.openservices.tablestore.tunnel.worker.DefaultChannelProcessor.process(DefaultChannelProcessor.java:29)
at com.alicloud.openservices.tablestore.tunnel.pipeline.ProcessDataPipeline$2.doProcess(ProcessDataPipeline.java:153)
at com.alicloud.openservices.tablestore.tunnel.pipeline.ProcessDataPipeline$2.doProcess(ProcessDataPipeline.java:147)
at com.alicloud.openservices.tablestore.tunnel.pipeline.AbstractStage.process(AbstractStage.java:29)
at com.alicloud.openservices.tablestore.tunnel.pipeline.ThreadPoolStageDecorator$1.run(ThreadPoolStageDecorator.java:29)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:266)
at java.util.concurrent.FutureTask.run(FutureTask.java)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.IOException: Connection reset by peer
at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
at sun.nio.ch.IOUtil.read(IOUtil.java:192)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:377)
at io.netty.buffer.PooledByteBuf.setBytes(PooledByteBuf.java:253)
at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1133)
at io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:350)
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:148)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:714)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
... 1 common frames omitted

The JanusGraph server did't print any error log.I try to modify `gremlin-server.yaml` about maxContentLength. But it didn't work. What caused this Error? Gremlin Server? JanusGraph? Who has had this problem? What's the solution?
1621 - 1640 of 6678