Zimbra SOAP Request to create user always end up in the same store

[bacacosta]

Hello everybody,

I'm trying to understand better how this whole balancing process from Zimbra works. Now we are facing a new problem: we have 3 stores (let's call them store1, store2 and store3). Even though we send all our create user requests to store2, store1 is the one that is always overload, as if store2 has sent these requests to store1 for processing. Is it possible? How can i specify which store should process a request?

Thanks a lot for your help!
Rodrigo

[uxbod]

It will be dependent on what you have specified within the CoS for which the new users are associated with. Check in the Admin GUI under CoS -> Server Pool and see whether you have

Do not limit server pool available for creating new users in this COS:
Limit server pool available for creating new users in this COS to:

I believe if you have defined three stores and have set the do not limit option it should round-robin between them when accounts are created.

[bacacosta]

Hello uxbod, and thanks for the quick reply. We have all stores activated in the pool, and the users are rightly created in one of them, randomly. But it seems like that store1 ist processing all the requests, because only it has such a high load at this moment. The other 2 remain pretty low.

[uxbod]

Have the other two mailstores been added as you have grown ? By design the mailboxes will not automatically migrate to another mailstore if it is fully loaded. The best option would be to get a list of the number of accounts within each store and then manually balance them account.

[bacacosta]

Yes, the store that remais high is the first store, the other two were added later... But what i find really amazing is, that now the 'problematic' store is *out of the pool*, but its load continues much higher then the other ones (like 10 times higher). The stores have now about the same amount of accounts each, and i can assure u that this requests come from registration (because if we shut the registration down, the load goes down at the same moment, and if we activate it again, it goes up). Also, i have the logs with this requests.

Is it possible that Zimbra always process CreateUserRequests on the first installed store, even if it is not in pool and if the request is sent to any other store?

I really can't understand what's happening here...

[raj]

<CreateAccountRequest xmlns="urn:zimbraAdmin">
<name>TEST@DOMAINNAME.COM</name>
<password>MYPASSWORD</password>
<a xmlns="" n="givenName">FULL NAME</a>
<a xmlns="" n="displayName">DIPLAY NAME</a>
<a xmlns="" n="zimbraMailQuota">10240000</a>
<a xmlns="" n="zimbraMailHost">mymailstore.mydomainname.com</a>
</CreateAccountRequest>"

when creating user you can tell the SOAP which mailbox to use from your pool.

Raj

[bacacosta]

Hello Raj, thanks for ur reply. I know about this option already, but this is not my problem. The store with the high load *is not in the pool*. It receives no request (or should not at least) from registration, but as soon as i turn the registration on, its load goes really high, although, again, *it's not in pool*!!! How is it possible?