Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • stork stork
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 276
    • Issues 276
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 25
    • Merge requests 25
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • storkstork
  • Issues
  • #398
Closed
Open
Issue created Sep 07, 2020 by Peter Davies@peterdDeveloper

Stork cannot connect large Kea installation

name: Stork cannot connect large Kea installation 
about: Stork 0.10 is unable to connect to agent when there a large number of subnets defined in Kea (1.8).

KEA 1.8.0 today and installed Stork 0.10, I noticed that Stork server can't connect to my large instances (with ~4500 subnets) and I see the following errors logged in Events tab:

grpc manager is unable to re-establish connection with the agent 192.168.1.5:8080: rpc error: code = ResourceExhausted desc = grpc: received message larger than max (4607854 vs. 4194304)

RT #17072

Comments:

According to the gRPC doc there are two functions to set maximum sizes:

  • MaxCallRecvMsgSize
  • MaxCallSendMsgSize

The default seems to be 4MB (confirmed by the error message).

Another idea is to use compression: JSON should be very easy to compress efficiently...

Edited Sep 08, 2020 by Peter Davies
Assignee
Assign to
Time tracking