Hot spots in vertex index table about hgraphdb

[rayokota]

Yes, it is possible to get hotspots when using vertex indices with many vertices with the same label. Currently the vertex index is not hashed/salted in order to support range queries and pagination on vertex indices. It would be possible in the future to add an option to create vertex indices that do not support range queries and pagination, so that they can be salted.

[youzp]

@rayokota thanks for your help. I do not need range queries and pagination, is there any simple way to solve this problem now? I used a different label but it didn't work, because rowkey of vertex index table always has a fixed prefix of "4", very strange!

[rayokota]

I've modified the vertex index format so that the combination of label and property key is salted. This will still mean hotspots if you use the same label and property key, but should otherwise distribute vertex indices among region servers. You will need to drop any existing vertex indices while on 1.x and recreate them after upgrading to 2.x.

[teenyboy]

but how can i design the label when I presplit the hbase table by HexStringSplit style ? the system don't need the range query and pagination .
Thank you for taking the time to answer me!

[rayokota]

@teenyboy , unfortunately, if you frequently use the same label and property key for a vertex index, you may encounter hotspots.