1. Janusgraph-Users
  2. Topics

Block ID pool allocation

rafi ansari <rafi1...@...>
 

Hi

I want to set my Janusgraph instance to read-only mode and stop id pool allocation to the instance.

For read-only mode, I can use storage.read-only=true. 
But is there any way to stop the ID pool allocation to the instance?

TIA

Rafi
sparshneel chanchlani <sparshneel...@...>
 

Rafi,
There is also an option for creating read only transactions TransactionBuilder  take a look.  Instead doing this on storage backend.

On 05-Jul-2020, at 13:44, rafi ansari <rafi1...@...> wrote:

Hi

I want to set my Janusgraph instance to read-only mode and stop id pool allocation to the instance.

For read-only mode, I can use storage.read-only=true. 
But is there any way to stop the ID pool allocation to the instance?

TIA

Rafi

--
You received this message because you are subscribed to the Google Groups "JanusGraph users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgra...@....
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-users/3c5e2cbb-1749-4a78-b2ea-bca893ca8608o%40googlegroups.com.
rafi ansari <rafi1...@...>
 

Hi Sparshneel

Thanks for suggestion. I explored the transactionbuilder read-only function. I have two doubts though .
1. What is the difference between setting storage as read-only and transaction read-only?
2. How do make sure that ID pool allocation is blocked on the Janusgraph read-only instance?

Because what I'm trying to achieve here is setting 2 nodes that will only act as read only nodes for Janusgraph.

Thanks

Rafi
sparshneel chanchlani <sparshneel...@...>
 

Rafi,
with graph instance you could create objects like vertexLables etc.. ID allocation only happens when u request to create. Read-Only transaction will through exception when u send create request to Janusgraph.


On Sun, Jul 5, 2020, 5:03 PM rafi ansari <rafi1...@...> wrote:
Hi Sparshneel

Thanks for suggestion. I explored the transactionbuilder read-only function. I have two doubts though .
1. What is the difference between setting storage as read-only and transaction read-only?
2. How do make sure that ID pool allocation is blocked on the Janusgraph read-only instance?

Because what I'm trying to achieve here is setting 2 nodes that will only act as read only nodes for Janusgraph.

Thanks

Rafi

--
You received this message because you are subscribed to the Google Groups "JanusGraph users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgra...@....
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-users/92767342-b5b3-4fca-9b75-feeab48f2b73o%40googlegroups.com.
sparshneel chanchlani <sparshneel...@...>
 



On Sun, Jul 5, 2020, 5:15 PM sparshneel chanchlani <sparshneel...@...> wrote:
Rafi,
with graph instance you could create objects like vertexLables etc.. ID allocation only happens when u request to create. Read-Only transaction will throw exception when u send create request to Janusgraph.

On Sun, Jul 5, 2020, 5:03 PM rafi ansari <rafi1...@...> wrote:
Hi Sparshneel

Thanks for suggestion. I explored the transactionbuilder read-only function. I have two doubts though .
1. What is the difference between setting storage as read-only and transaction read-only?
2. How do make sure that ID pool allocation is blocked on the Janusgraph read-only instance?

Because what I'm trying to achieve here is setting 2 nodes that will only act as read only nodes for Janusgraph.

Thanks

Rafi

--
You received this message because you are subscribed to the Google Groups "JanusGraph users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgra...@....
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-users/92767342-b5b3-4fca-9b75-feeab48f2b73o%40googlegroups.com.

1 - 5 of 5