Forum Discussion

sechet-q's avatar
sechet-q
New Member
3 years ago

On premise Datagateway cluster member max

Hello everyone,

 

I can't seem to find the article about scalability again in the doc, but anyway i'm fairly sure that it didn't contained th answer i'm looking for.

 

So, here is my question : It seems that a cluster of on premise-datagateway have a maximount amount of member, but i cannot find a written statement about that.

I actually cannot put more than 5 members in a cluster. From what i have gathered, the previous admin could only put 2.

I believe that it should be tie to our capacity. (we actually have four capacity, so it would be C+1 ? )

 

Can anyone confirm that, or show me where i can find the written information?

 

thanks in advance.

4 Replies

  • That is incorrect. Gateways are independent of the capacity. We were running gateways with 10 cluster members until we understood that that is overkill, and it is better to have fewer cluster members with better specs (32 GB RAM, 16 cores, SSDs).  But there is no limit that I am aware of.

  • Well, that is strange.

     

    I clearly remember having an error message which was related to the capacity, but i cannot found a screenshot of it.

    I tried to reproduce it and ... magic, i dont have an error and i was able to put 10 machines in the cluster ...

    I guess that something has changed from our side but well whatever ...

     

    Thanks for the help anyway.

    • sechet-q's avatar
      sechet-q
      New Member

      AH! I knew that it was saved somewhere.

      Here is the error i got when i previously tried to add more than 5 machines in my cluster :

       

      "One or more capabilities need to be configured for this Gateway to match the overall capabilities of the cluster.
      Unmatched static capabilites: 16777216."

       

      Eventually, it disappeared, meaning that some kind of action probably was done somewhere !

      • lbendlin's avatar
        lbendlin
        Icon for Super User rankSuper User

        Quite a peculiar error message. I have not encountered that one ... yet.