Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Kea Kea
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 556
    • Issues 556
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 66
    • Merge requests 66
  • 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
  • KeaKea
  • Issues
  • #114
Closed
Open
Issue created Sep 10, 2018 by Tomek Mrugalski@tomek🛰Owner

Timeouts specified in inconsistent units

According to our documentation, timeouts for MySQL and PostgreSQL are specified in seconds, while the same values for CQL are in milliseconds.

I think it's better to use milliseconds. The use case for this is that in HA scenarios, sometimes waiting for a second is too much and sub-second precision may be needed. Milliseconds is also the units used in HA.

The immediate reason why this popped up is NETCONF model definition. However, our current documentation probably should be improved as well. We currently have the parameters explained several times, once for each backend.

Parameters affected: connect-timeout, reconnect-wait-time, request-timeout. There may be others I missed.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking