Hi,
no one here who is able to reply to my questions?
Regards
Patrick
Patrick Westenberg schrieb:
Hi everyone,
short version:
Is there no built in failover mechanism for the director service to
handle a backend failure?
Long version:
I have a frontend server running the director service
People already replied and pointed to poolmon. There is no built-in failure
handling, because it's not possible to implement it in a way that works well
for everyone. Although I think poolmon could also itself use a bit of tweaking.
For example if all hosts became very heavily loaded, poolmon
l...@airstreamcomm.net wrote:
Considering the intention of the director was to alleviate locking
issues in a shared storage environment are there any current
solutions to improving the scalability/availability of Dovecot by
implementing an alternative message storage systems such as nosql or
On 10/21/12 2:43 PM, Daniel Parthey wrote:
Patrick Westenberg wrote:
Is there no built in failover mechanism for the director service to
handle a backend failure?
No, the director's job is to keep a hash table and direct
the connection for each user to its associated backend.
Currently, there
Hi everyone,
short version:
Is there no built in failover mechanism for the director service to
handle a backend failure?
Long version:
I have a frontend server running the director service and two backends.
Due to maintenance I had to shut down one of the backends which caused
connection
Patrick Westenberg wrote:
Is there no built in failover mechanism for the director service to
handle a backend failure?
No, the director's job is to keep a hash table and direct
the connection for each user to its associated backend.
Currently, there is no built-in backend monitoring.
In order
