Re: Getting org.janusgraph.graphdb.database.idassigner.IDPoolExhaustedException consistently
There does not seem to be much that helps in finding a root cause (no similar questions or issues in history). The most helpful thing I found is the following javadoc:
Assuming that you use this default SimpleBulkPlacementStrategy, what value do your use for ids.num-partitions ? The default number might be too small. In the beginning of a spark job, the tasks can be more or less synchronized, that is they finish after about the same amount of time and then cause congestion (task number 349 ...). If this is the case, other configs could help too:
ids.renew-percentage If you increase this value, congestion is avoided a bit, but this cannot have a high impact.
ids.flush I assume you did not change the default "true" value
ids.authority.conflict-avoidance-mode Undocumented, but talks about contention during ID block reservation
Best wishes, Marc