Hi,
The docs says that "A cluster is a generic way to group records". Create
class command definitely has the cluster definition. What I'm missing ? I
think that "node" semantic was replaced by "cluster" at some time during
development. It will be good to have the right definition of the OrientDB
node that holds the records, its clusters and classes. Can you please give
it ? Or point to some OrientDB docs about the classes/clusters/nodes and
their clear relations ?
Thanks !
P.S. Seems like "ALTER CLASS class1 CLUSTERSELECTION local" sets the
selection to round-robin (v2.1.16). Anyway I think balanced mode was
created for sharding purposes, so why it is not possible to have the same
cluster balanced over serveral nodes ?
понедельник, 25 апреля 2016 г., 7:51:57 UTC+3 пользователь Hung Tran
написал:
>
> Hi TIA,
>
> You may be confused between node cluster (distributed) and class cluster
> (local).
>
> My Best,
> Hung Tran
>
> On Monday, April 25, 2016 at 2:10:03 AM UTC+7, Sfinx wrote:
>>
>> Hi Luca,
>>
>> It is still not clear can the different classes be located at the same
>> cluster ? As of v2.1.16 seems like this is impossible :
>>
>> ....
>> *create database plocal:/opt/orientdb/databases/db1 root root_pass;*
>> *create cluster clust1;*
>> *create class class1 extends V cluster clust1;*
>>
>> *create class class2 extends V cluster clust1; *<=== error
>>
>> *Error: com.orientechnologies.orient.core.exception.OSchemaException:
>> Class*
>> *class2 already exists in current database*
>>
>> Grouping several classes in the same cluster is impossible, but we can
>> *remove
>> all the clusters from the class* !
>>
>> *orientdb {db=db1}> info class class2*
>>
>> *CLASS 'class2'*
>>
>> *Super classes........: [V]*
>> *Default cluster......: class2 (id=12)*
>> *Supported clusters...: class2(12) *
>> *Cluster selection....: round-robin*
>> *Oversize.............: 0.0*
>> *orientdb {db=db1}> info class class2*
>>
>> *orientdb {db=db1}> alter class class2 removecluster class2;*
>>
>> *Class updated successfully*
>>
>> *orientdb {db=db1}> info class class2*
>>
>> *CLASS 'class2'*
>> *Super classes........: [V]*
>> *Default cluster......: null (id=-1)*
>> *Supported clusters...: *
>> *Cluster selection....: round-robin*
>> *Oversize.............: 0.0*
>> *orientdb {db=db1}> *
>>
>> Is this behavior expected ? If yes - can somebody explain the logic
>> behind it ?
>>
>> I'd like to have some classes located inside the same cluster. Is it
>> possible ?
>>
>> TIA
>>
>> пятница, 26 февраля 2016 г., 19:06:12 UTC+2 пользователь l.garulli
>> написал:
>>>
>>> Hi Scott,
>>> We will increase this limitation in v3.0, with the chance to have up to
>>> 2^16 clusters. If now you have this problem (even though having more than
>>> 2,000 classes is 1% of use cases) you can force OrientDB to have less
>>> clusters per class by executing:
>>>
>>> ALTER DATABASE MINIMUMCLUSTERS 1
>>>
>>> Or any number instead of 1.
>>>
>>>
>>>
>>> Best Regards,
>>>
>>> Luca Garulli
>>> Founder & CEO
>>> OrientDB <http://orientdb.com/>
>>>
>>>
>>> On 26 February 2016 at 13:00, 'scott molinari' via OrientDB <
>>> [email protected]> wrote:
>>>
>>>> A polite bump. :-)
>>>>
>>>> Scott
>>>>
>>>> --
>>>>
>>>> ---
>>>> 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.
