You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Experienced
Having edge routers go down will remove active sessions that have no possible route at the fabric level. Querying for the sessions via the Edge API will still show the session active. Clients of that session will not know it is invalid when querying the Edge API.
Expected
If the fabric removes a session, that is reflected in the Ede API
Reproduction
Create a service w/ only 1 edge router that can handle it
Connect everything (edge router, sdk, controller)
Stop the edge router
Use ziti-fabric list session and GET /sessions to compare.
The text was updated successfully, but these errors were encountered:
Experienced
Having edge routers go down will remove active sessions that have no possible route at the fabric level. Querying for the sessions via the Edge API will still show the session active. Clients of that session will not know it is invalid when querying the Edge API.
Expected
If the fabric removes a session, that is reflected in the Ede API
Reproduction
ziti-fabric list session
andGET /sessions
to compare.The text was updated successfully, but these errors were encountered: