In scylla grafana board, this issue is seen with high number of foreground read tasks.

Thank you folks for getting back. @Simone3, yes this issue comes out as read timeout from the shard holding the system_properties table (there is only 1 partition for system_properties

Hi all We are using janusgraph at zeotap at humongous scale (~70B V and 50B E) backed by scylla. Right now I am facing an issue in janusgraph_ids table, wherein there are large partitions created in

On Mon, Feb 15, 2021 at 05:59 AM, sauverma wrote: zeotapHi Saurabh, we are experiencing the exact same issue: spark job with one janusgraph instance per partition calling a scylladb cluster. Our

Hi Saurabh! Thanks for reporting that issue! Looking at the open pull requests, I don't see one that addresses this problem. You're always welcome to share your solutions by discussing them here or

Hi all - The interaction with the underlying KV store via janusgraph client hits the `system_properties` table with a range query where the key is `configuration` (key = 0x636f6e66696775726174696f6e)

Ahh. Actually think I may have answered my own question building from source. Looks like hadoop:2.7.7 and spark-gremlin:3.4.10 are still using netty 3 and the POM just bumped to the latest netty 3

Noticed that there are two versions of Netty in the POM for JanusGraph: - version 3:https://github.com/JanusGraph/janusgraph/blob/master/pom.xml#L806 & - version 4:

Hello, I'm working on planning another JanusGraph community meetup and wanted to gauge community interest in doing an in-depth focus on tackling OLAP/graph algorithmic work with JanusGraph. This has

Sounds like a good thing to do. We should consider updating our documentation (#54) before that, so that users who get started with the new release don't experience any issues regarding installation

Hi all, I think we should consider doing a release of the janusgraph-foundationdb adapter sometime soon. There have been several changes since the initial 0.1.0 release that warrant a new release.

I also now find groups.io to be not as good experience as Google Groups. 1) As noted by Marc, there is no way to see on UI that there are threads with new messages you didn't see. Here is the issue

Hi Marc, > 1. After a new reply appears to a thread, the thread still appears as "read" in the web ui. In other words, you have to open every thread to see whether new replies are present. That's

Hi all, After using the new mail lists through the web ui for a while, there are two aspects that are particularly annoying: 1. After a new reply appears to a thread, the thread still appears as

I think it would be just okay to have a monthly repeating meeting. Do we also want to use a google document to keep notes?

The default option is now `Reply to Group`

As we are now under LF AI & Data, we can ask for Zoom account for regular JanusGraph meetings.

Hi Marc, It definitely makes sense to prioritize "Group Reply". I requested John Mertic to change the default option to `Group Reply`. I'm also voting +1 to remove the option `Reply to Sender`. Best

The new mailing list stimulates users to use the option "reply to sender". This means that discussions between OP and expert become invisible to other users. It also means that experts cannot answer

The janusgraph user forum was moved to: https://lists.lfaidata.foundation/g/janusgraph-users You have to fill an e-mail address and acknowledge a request sent to that address. Regarding the code lines