Open amyth opened 7 years ago
any changes on this?
any update here?? I am getting exactly the same exception
The issue is related to lock write time being more than 100ms. Most likely your gremlin server is located too far from bigtable servers. Please, change 'storage.lock.wait-time' to a bigger value (maybe something like 5000).
@mbrukman Do you think we should increase the default value to a bigger value (like 1-2 seconds instead of 100 ms) so that new users would not get this common exception?
@porunov I tried setting it to 5000. Its still not working, now i get the exception below org.janusgraph.diskstorage.TemporaryBackendException: Could not successfully complete backend operation due to repeated temporary exceptions after PT1M40S
By the way i am using cassandra as backend store and elastic for index store see the configuration below
tx.log-tx=true tx.max-commit-time=15000
metrics.enabled=False metrics.jmx.enabled=False
cluster.max-partitions=32
storage.lock.expiry-time=3000
storage.lock.wait-time=5000
storage.lock.retries=10
ids.block-size=100000
Try to check that "repeated temporary exceptions". Maybe there are some information. Hard to answer without seeing the whole picture.
That being said. You "repeated temporary exceptions" are not related to this issue. Try to find help on users google group: https://groups.google.com/forum/#!forum/janusgraph-users
@porunov thanks it worked. Lock expiry time was not set correctly after i set wait time to 5000
@porunov wrote:
@mbrukman Do you think we should increase the default value to a bigger value (like 1-2 seconds instead of 100 ms) so that new users would not get this common exception?
@kolea2 and @igorbernstein2 are looking into issues with Cloud Bigtable driver for JanusGraph; I'll let them comment on what they think is the best approach here.
I'm not very familiar with janus graph, but have a bit of knowledge on the java client. What operation does this timeout map on to?
I'm not very familiar with janus graph, but have a bit of knowledge on the java client. What operation does this timeout map on to?
It's time to wait to lock to be written on a storage backend. It is used when you are defining your schema (creating new vertex labels, edge labels, properties keys, indices).
Also, I think it may be used when you dealing with locks in general (but not sure on this one). For example, when you have an index with unique
key but your storage backend is eventually consistent. For eventually consistent storage backends JanusGraph acquires a lock when writing new data which is used by an index with unique
property defined.
Hey, I am using janusgraph with bigtable backend and am trying to create a property key. As soon as I commit this transaction using
management.commit()
, I get the following error:How to reproduce
To reproduce this, just get the
janusgraph
up and running withbigtable
storage backend and do the following within gremlin shell:Update: Version & Config Information
bigtable-hbase-1.x-hadoop-1.0.0-pre2.jar
,netty-tcnative-boringssl-static-1.1.33.Fork26.jar
)Configuration is as follows: