When is Google intending to fix this major problem?
I am in the red with the amount of stored data caused by the
_ah_session object, which should be cleaned up by the servlet
container.
As you seem to know, the SessionCleanupServlet fails when the dataset
is too big, which is my case.
When can de
Nevermind -- looks like a wide spread problem, being discussed on the
appengine list already ...
On Tue, Feb 2, 2010 at 9:07 AM, Dombrowski, Todd wrote:
> Most likely indexes -- "app engine maintains an index for every query the
> app engine will perform" (from Programming Google App Engine)
>
>
Most likely indexes -- "app engine maintains an index for every query the
app engine will perform" (from Programming Google App Engine)
If you have a variety of queries that use multiple properties and sort
orders, the datastore will need an index for every unique combination -- and
this is in add
Hi Dimitar,
This is an idea. Take a closer look to your _ah_SESSION kind. It is
possible you are storing huge session data and it remains there after
the sessions expire. If that is the case, you probably want to clean
your expired sessions periodically.
Jorge Gonzalez
On Feb 1, 1:05 pm, dmakar
Hi again,
I've read the documentation. and cannot find anything related to my
datastore growth :(,
I'm not using indexes. It is quite simple application, demonstrating
the usage of JSF 2. I'm using session, and I've included the
SessionCleanupServlet in my web.xml. It is started every hour.
So the
