[18.09] cluster: set bigger grpc limit for array requests

[andrewhsu]

backport:

• cluster: set bigger grpc limit for array requests moby/moby#38103 cluster: set bigger grpc limit for array requests

to address:

• docker service ls | Error response from daemon: rpc error: code = ResourceExhausted desc = grpc: received message larger than max (5097134 vs. 4194304) moby/moby#37997 docker service ls | Error response from daemon: rpc error: code = ResourceExhausted desc = grpc: received message larger than max (5097134 vs. 4194304)

git cherry-pick moby@489b8ed

$ git cherry-pick -s -x 489b8eda6674523df8b82a210399b7d2954427d0
[grpc 6ca0546f25] cluster: set bigger grpc limit for array requests
 Author: Tonis Tiigi <tonistiigi@gmail.com>
 Date: Mon Oct 29 17:44:11 2018 -0700
 3 files changed, 13 insertions(+), 5 deletions(-)

no conflicts

[thaJeztah]

@andrewhsu the upstream PR was updated (only the commit message); can you cherry-pick the new commit? moby@f1f50ed f1f50eddae5e15c0f5fd3b7f16fa7fef253f869c

[thaJeztah]

LGTM

Also addresses moby#37941. Related: moby#36895 (pull request that brought in the updated grpc version) moby/swarmkit#2774 (tracking issue for looking at the message size)

[rnz]

dockerd[2888]: time="2019-03-27T02:27:29.990822362+03:00" level=error msg="agent: session failed" backoff=100ms error="rpc error: code = ResourceExhausted desc = grpc: received message larger than max (4270560 vs. 4194304)" module=node/agent node.id=7wittan6h0xbkva01kuy1empm

Server Version: 18.09.3
Kernel Version: 4.19.0-0.bpo.2-cloud-amd64
Operating System: Debian GNU/Linux 9 (stretch)
Architecture: x86_64

docker service list | wc -l 667

[vsenapathy]

Is this fix part of 18.09.9? also i see that @rnz got an error on 18.09.3. So i have a around 600 services also. Will i get the same error