I noticed that the property is _expires _ah_SESSIONindexed. This is very useful when requesting expired sessions. But this seems to be a drawback. The property _expirescontains monotonically increasing values. This means that index entries for this property are likely to end up on the same tablet server. I am concerned that such a tablet server might be easily overloaded with applications that frequently update session data. Is there a way to tell App Engine NOT to index a property _expires? Perhaps something like adding a rule to appengine-web.xml, for example:
<session-index-expiration>false</session-index-expiration>
As far as I know, the answer to my question is no. I am thinking of providing a function request. But maybe I missed something. Your input will be much appreciated.
Update 1: I requested this feature. Please consider voting for the “lead”: https://issuetracker.google.com/issues/71583968
Update 2: The feature request has been noticed by Google and the “solution is being investigated.” There is a message in the discussion about the problem tracker that says that it may be possible to prevent the indexing of the property _expiresusing a configuration file datastore-indexes.xml. However, since this file apparently deals exclusively with declaring custom indexes, I don’t see how it can be used to disable a single property index. Any ideas?
PS: , , _ah_SESSION . . SessionManager, , 25%. , _expires. , , .