On Tue, Apr 17, 2018 at 9:32 AM, Sergei Gerasenko wrote:
> 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?
>
I haven't played with the workers op
> 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
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 JAVA/JAAS clients caching the TGT and not the service
> tickets. Es
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 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 JAVA/JAAS clients caching the TGT and not the service
tickets. Especially in Hadoop envi
