If you don't put the cluster entry in JSON file the "*" is taken, and by
default means replicate against all the nodes.
So do like "internal" cluster removing the "servers" property:
"Client": {
},
Lvc@
On 18 July 2014 18:14, galina manashirova <[email protected]>
wrote:
> Hi Luca;
> Thank you for your reply.
> What if I want to exclude class Client from replication? I would for
> example replicate everything, but not that particular class (classes)?
> Is there anyway to set it up? Or the only way to do it just to list
> everything which needs to be replicated, whatever is not in the list will
> not get replicated?
> Is that correct?
>
> -galina
>
> On Friday, July 18, 2014 2:58:26 AM UTC-7, Lvc@ wrote:
>
>> Hi,
>> Is this question the same like the previous one?
>>
>> About your question this is the default cfg (config/default-distributed-
>> db-config.json):
>>
>> {
>> "autoDeploy": true,
>> "hotAlignment": false,
>> "readQuorum": 1,
>> "writeQuorum": 2,
>> "failureAvailableNodesLessQuorum": false,
>> "readYourWrites": true,
>> "clusters": {
>> "internal": {
>> },
>> "index": {
>> },
>> "*": {
>> "servers" : [ "<NEW_NODE>" ]
>> }
>> }
>> }
>>
>> As you can see al the clusters ("*") are replicated on each new servers.
>> If you have the class *Client* that works against 2 clusters *client_usa*
>> and *client_europe* you can do this:
>>
>> {
>> "autoDeploy": true,
>> "hotAlignment": false,
>> "readQuorum": 1,
>> "writeQuorum": 2,
>> "failureAvailableNodesLessQuorum": false,
>> "readYourWrites": true,
>> "clusters": {
>> "internal": {
>> },
>> "index": {
>> },
>> "client_usa": {
>> "servers" : [ "usa" ]
>> }
>> "client_europe": {
>> "servers" : [ "europe" ]
>> }
>> "*": {
>> "servers" : [ "<NEW_NODE>" ]
>> }
>> }
>> }
>>
>> So all the operation against client_usa will go to the server "usa".
>> Every time you execute a query against the class Client, a Map/Reduce like
>> query is executed against both servers.
>>
>>
>> Lvc@
>>
>>
>>
>> On 17 July 2014 21:32, galina manashirova <[email protected]> wrote:
>>
>>>
>>> Hi;
>>>
>>> 1. One of requirements in regards of replication is to be able to
>>> set replication on each data element’s level, whether it is replicated or
>>> not.
>>>
>>> We don’t replicate some data which are always local and we need a
>>> flexible way to turn it on and off at the lowest data level. Can we do
>>> it by just configuring Orient Db or it has to be done on Java API level ?
>>> What would be your recommendation and how would you handle it?
>>>
>>>
>>> Thank you!
>>>
>>> -galina
>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "OrientDB" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OrientDB" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
