12 Commits (b5e811148540747d5d08c6e35f509f485dd88093)

Author	SHA1	Message	Date
Atin Malaviya	ac54010027	Fixed clearSessionTimer, created invalidateSession, added invalid TTL test	10 years ago
Atin Malaviya	60915629f6	Took out usage of snapshot SessionListTTL	10 years ago
Atin Malaviya	0f9723e6f8	Remove hardcoded wait time in session TTL tests	10 years ago
Atin Malaviya	5229f3b44d	Clean up code based on feedback from armon	10 years ago
Atin Malaviya	624c465e2b	Added more tests. Also added return of 404 if the session id to renew is not found	10 years ago
Atin Malaviya	4732c36d88	Consul Session TTLs ... The design of the session TTLs is based on the Google Chubby approach (http://research.google.com/archive/chubby-osdi06.pdf). The Session struct has an additional TTL field now. This attaches an implicit heartbeat based failure detector. Tracking of heartbeats is done by the current leader and not persisted via the Raft log. The implication of this is during a leader failover, we do not retain the last heartbeat times. Similar to Chubby, the TTL represents a lower-bound. Consul promises not to terminate a session before the TTL has expired, but is allowed to extend the expiration past it. This enables us to reset the TTL on a leader failover. The TTL is also extended when the client does a heartbeat. Like Chubby, this means a TTL is extended on creation, heartbeat or failover. Additionally, because we must account for time requests are in transit and the relative rates of clocks on the clients and servers, Consul will take the conservative approach of internally multiplying the TTL by 2x. This helps to compensate for network latency and clock skew without violating the contract. Reference: https://docs.google.com/document/d/1Y5-pahLkUaA7Kz4SBU_mehKiyt9yaaUGcBTMZR7lToY/edit?usp=sharing	10 years ago
Atin Malaviya	6ef03a806c	Clean up tests, use switch to default session.Behavior value if unspecified, unrecognized	10 years ago
Atin Malaviya	47241fc1c8	Ephemeral Nodes for via Session behavior settings. ... Added a "delete" behavior for session invalidation, in addition to the default "release" behavior. On session invalidation, the sessions Behavior field is checked and if it is set to "delete", all nodes owned by the session are deleted. If it is "release", then just the locks are released as default.	10 years ago
Ryan Uber	149656951d	agent: fix tests after default status change	10 years ago
Armon Dadgar	10f3007aa2	consul: Adding support for optional session name	11 years ago
Armon Dadgar	00a107dfd9	agent: Adding support for specifying LockDelay, defaults to 15 seconds.	11 years ago
Armon Dadgar	c071932f92	agent: Session endpoint tests	11 years ago