fix --min-np and --max-np args in elastic example

[zw0610]

Fix the missing -- before min-np and max-np.

[gaocegege]

I am wondering how to support autoscale with HPA in the future. If we change the spec.replicas to 100, what will happen?

[terrytangyuan]

Approving this so the example would at least work. We should probably discuss the case of HPA in a separate thread.

/approve
/lgtm

[google-oss-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: terrytangyuan, zw0610

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [terrytangyuan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[zw0610]

--max-np sets the max processes count. If replicas number exceeds max-np, redundant slots will be ignored. To support HPA, users needs to give a large number to max-np in launcher pod command.

…

On Wed, Mar 10, 2021, 18:50 Ce Gao ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In examples/horovod/tensorflow-mnist-elastic.yaml <#338 (comment)>: > - "1" - - max-np + - --max-np I am wondering how to support autoscale with HPA in the future. If we change the spec.replicas to 100, what will happen? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#338 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AK7V6IQAXNNVDMOIIEI6WSDTC5FHJANCNFSM4Y5TITQA> .