Hi,
I’m planning an MIT KDC installation for a hadoop cluster consisting of X
clients with Y kerberized services each. The KDCs are rather powerful machines
with 64 cores and 125G of RAM. I want to get the most out of this hardware and
use the mininum number of KDCs required. Is there a rule of
:13 PM, Russ Allbery wrote:
>
> Sergei Gerasenko writes:
>
>> I’m planning an MIT KDC installation for a hadoop cluster consisting of
>> X clients with Y kerberized services each. The KDCs are rather powerful
>> machines with 64 cores and 125G of RAM. I want to get th
Hi Russ,
Since I don’t know too much about the KDC architecture, sorry for the
dilettante questions.
> It's unfortunately been long enough since I've tested this on a system
> running flat out that I don't remember what qps a KDC can do on modern
> hardware, but I would expect it to at least be
> Oh, no problem -- just be aware that they're being answered by someone who
> hasn't run large-scale KDCs in about four years, so some of my information
> is stale. :)
Still very valuable since I haven’t been able to find answers to any of these
questions elsewhere.
> If you're doing default K
Thank you so much for confirming that the KDCs are fast. This saved me a ton of
time writing my own tests, etc. Andrew, as far as workers, is it one worker per
core in general as Russ theorized?
Otherwise, I think I’m all set for now.
Thanks!!
> On Apr 16, 2018, at 8:41 PM, Russ Allbery wrote
> On Apr 17, 2018, at 5:20 PM, Russ Allbery wrote:
>
> Mark Pröhl writes:
>> On 04/16/2018 05:51 PM, Russ Allbery wrote:
>
>>> ... Clients aren't going to generally all try to get a ticket at the
>>> same time, due to ticket caching, so that scales to a lot of clients.
>
>> I have only seen J
