How JanusGraph balance habse storage #3318
Replies: 2 comments 4 replies
-
Relevant sections in the ref docs are:
Also note that automatic HBase compaction may "destroy" any planned partitioning. E.g. if you have 20 region servers that each store 1 GB of data after the initial load, HBase will try to compact that to one 20 GB region server if not configured otherwise. HBase can do this for overall cluster efficiency for all tables and applications it serves, but that will not profit your particular JanusGraph app. |
Beta Was this translation helpful? Give feedback.
-
When I do a google search on "decode janusgraph row key", the following result is ranked highest: You can give it a try. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I use Hbase as storeage backend. I don't know how Janusgraph choose id for a vertex.
I have a problem that request read and write on regions are differrent. Some regions have a large number of requests read, and some do the opposite. In general, they are not balanced
Can someone give me an idea to rebalance hbase?
Beta Was this translation helpful? Give feedback.
All reactions