The problem reported below proves to have been resolved by this change:
2797. [bug] Don't decrement the dispatch manager's maxbuffers.
[RT #20613]
When randomized query ports was implemented, the increase in the number
concurrently-used sockets had an equivalent increased usage need of
another re
On Wednesday 06 January 2010 12:49:46 Cathy Almond wrote:
> That's what I think is possibly happening in your case - one potential
> contributing factor being the configuration settings I suggested you
> check for. Somewhat obscure - sorry :-/
No need to be sorry - thank you for taking the time t
Imri Zvik wrote:
> On Wednesday 06 January 2010 11:56:13 Cathy Almond wrote:
>> Do you use any of the following in your configuration:
>>
>> transfer-source
>> transfer-source-v6
>> notify-source
>> notify-source-v6
>> query-source
>> query-source-v6
>
> No :) my configuration is '*source*' free,
On Wednesday 06 January 2010 11:56:13 Cathy Almond wrote:
> Do you use any of the following in your configuration:
>
> transfer-source
> transfer-source-v6
> notify-source
> notify-source-v6
> query-source
> query-source-v6
No :) my configuration is '*source*' free, And anyhow, even if I had it in
Hi Imri,
Do you use any of the following in your configuration:
transfer-source
transfer-source-v6
notify-source
notify-source-v6
query-source
query-source-v6
Regards,
Cathy
Imri Zvik wrote:
> Hi,
>
> We've recently upgraded our caching servers to 9.4.3-P4/P3 (2 of them running
> 9.4.3-P4 an
Hi,
We've recently upgraded our caching servers to 9.4.3-P4/P3 (2 of them running
9.4.3-P4 and 2 running 9.4.3-P3). Few days ago I've noticed something
strange - When the server is loaded, some queries randomly fails (SERVFAIL).
It seems that only queries for which the answer is NOT cached are
6 matches
Mail list logo
