![]() ![]() This is true for most API requests originating from user interaction with the Graylog UI because these will lead to an update of the session's "last access" timestamp. They will then notice that the session is gone. These nodes will only fail to accept the session id if they intent to update the session in the database. ![]() The other nodes will however still use the cached session. When the user logs out, the session is removed from the node-local cache and deleted from the database. However, each node maintains their isolated version of the session. Modifications to sessions will update the cached version as well as the session persisted in the database. After that, the node operates solely on the cached session. Upon a cache-miss, the session is loaded from the database. Each node maintains an in-memory cache of user sessions. In a multi-node Graylog cluster, after a user has explicitly logged out, a user session may still be used for API requests until it has reached its original expiry time. Graylog is a free and open log management platform.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |