CPU Count Drop On ECS

[Dave Harvey <dh...@jobcase.com>]

I was running a 8x i3.8xlarge cluster on AWS ECS, and it would normally display

^-- H/N/C [hosts=8, nodes=8, CPUs=256]


Then I recreated it and got this, and problems like I can no longer start visor.

^-- H/N/C [hosts=8, nodes=8, CPUs=8]


Our ECS task specifies CPU=0 -> 1 share.   I'm reverting the AMI to an
older version, but expect that the following was the trigger:


https://github.com/aws/amazon-ecs-agent/pull/1480

Disclaimer

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.

This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.

Re: CPU Count Drop On ECS

["ilya.kasnacheev" <il...@gmail.com>]

Hello!

I remember the discussion where Java 8 did not support detecting change of #
available CPUs. Then it improved in some of builds. Anyway, I think it's out
of our control since we rely on Runtime.availableProcessors(), unless this
issue becomes very widespread and we have to fix it on out side.

Still, there was an issue where Visor will use management thread pool
incorrectly and lock it down. The solution in your case will be to force
thread pool size to some constant number, like '4' or '8'. See
https://apacheignite.readme.io/docs/thread-pools but specifically you should
increase Management pool size.

Regards,



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: CPU Count Drop On ECS

[Dave Harvey <dh...@jobcase.com>]

Reverting the AWS AMI did not revert the ECS agent version.

On Fri, Oct 26, 2018 at 6:11 PM Dave Harvey <dh...@jobcase.com> wrote:

> I was running a 8x i3.8xlarge cluster on AWS ECS, and it would normally display
>
> ^-- H/N/C [hosts=8, nodes=8, CPUs=256]
>
>
> Then I recreated it and got this, and problems like I can no longer start visor.
>
> ^-- H/N/C [hosts=8, nodes=8, CPUs=8]
>
>
> Our ECS task specifies CPU=0 -> 1 share.   I'm reverting the AMI to an older version, but expect that the following was the trigger:
>
>
> https://github.com/aws/amazon-ecs-agent/pull/1480
>
>
>

Disclaimer

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.

This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.