2019, 12:53 Anton Puzanov, wrote:
> I have tried it right now and TLSv1 is still available. Running the
> openssl command shows the server certificate.
> I check for the protocols using nmap (-sV) which shows support for TLSv1,
> TLSv1.1, TLSv1.2
>
> On Tue, Sep 3, 2019 at 1
Can you share the output of below command?.
openssl s_client -connect hostname:8190 -tls1
Also, have you already tried below in custom yarn-site xml?
ssl.exclude.protocol=TLSv1,TLSv1.1
Thanks
On Mon, 2 Sep 2019, 20:22 Anton Puzanov, wrote:
> Hi,
>
> I have been requested to disable TLSv1 and
teStamps
> -Xms75776m -Xmx75776m
>
> On Thu, Feb 25, 2016 at 3:46 PM, bappa kon wrote:
>
>> Which garbage collector you are using currently in your env? Can you
>> share the jvm parameters?. If you are using CMS and already optimized your
>> parameter then probably
Which garbage collector you are using currently in your env? Can you share
the jvm parameters?. If you are using CMS and already optimized your
parameter then probably you can look at to G1 garbage collector.
First you should look at the GC stats and pattern to find out the cause of
long GC.
Reg
