the
>>> backend host completely. Or something, anything besides hosing things
>>> pretty badly.
>>>
>>> This is 2.2.27, on both the directors and backend. If the answer is
>>> upgrade to 2.2.28, then I'll upgrade immediately. I see
>>> commit a9a
f8bfde5dab0571afac mentions the same error but
>> the commit predates 2.2.27 by a month and a half.
>>
>> In the meantime, is there any doveadm command I could've done to fix
>> this? I tried removing the host (doveadm director remove 10.1.17.15) but
>> that did
ing the host (doveadm director remove 10.1.17.15) but that
> didn't do anything. I didn't think to try to flush the mapping for that
> user till just now. I suspect that with the ring unsync'd, flushing the
> user wouldn't have helped.
>
> The only remedy was to
#x27;t have helped.
The only remedy was to kill dovecot on every box in the director cluster
and then (with dovecot down on *all* of them) start dovecot back up.
Restarting each director's dovecot (with other directors' dovecots still
running) did nothing. Only by brining the entire cluster dow
