Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve Teleport availability and resiliency #1071

Closed
russjones opened this issue Jun 12, 2017 · 1 comment
Closed

Improve Teleport availability and resiliency #1071

russjones opened this issue Jun 12, 2017 · 1 comment
Milestone

Comments

@russjones
Copy link
Contributor

At the moment we have the following problems with Teleport.

  • there was in-memory cache that was only invalidated on server restart.
  • in case if all auth servers are down, no new SSH sessions could be created

We should improve it in the following ways:

  • teleport provides explicit control over cache TTL for Proxy and Node
  • cache is persistent and on-disk
  • in case if all auth servers are down, all systems including Proxy (reverse tunnels, etc) and Nodes are functioning
  • introduces throttling for failed auth servers to avoid locks on connection timeouts
  • introduces client-side caching for discovery data
  • introduces new expires metadata property uniformly supported by all resource objects
@russjones russjones added this to the 2.2 milestone Jun 12, 2017
@russjones
Copy link
Contributor Author

Fixed in #853

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant