Limitation on “Exceeded maximum allocated IDs”

[GoSharp Lite]

Issue 9110:

Application ID : gochild2009.appspot.com


My app is running fine for months. Today it starts to give error on "Exceeded maximum allocated IDs" with datastore put. Is this something new with appengine quota and limitation? What is the quota for allocated IDs?

[GoSharp Lite]

This might be a JDO limitation. Is there a setting to increase maximum allocation IDs?

java.lang.IllegalArgumentException: Exceeded maximum allocated IDs

at org.datanucleus.api.jdo.NucleusJDOHelper.getJDOExceptionForNucleusException(NucleusJDOHelper.java:488)

at org.datanucleus.api.jdo.JDOPersistenceManager.jdoMakePersistent(JDOPersistenceManager.java:736)

at org.datanucleus.api.jdo.JDOPersistenceManager.makePersistent(JDOPersistenceManager.java:756)

[Ian Marshall]

What is the relevant code (and values) that experience this exception?


On Apr 4, 10:13 am, GoSharp Lite <gosharpl...@gmail.com> wrote:
> *This might be a JDO limitation. Is there a setting to increase maximum
> allocation IDs?*

>
> java.lang.IllegalArgumentException: Exceeded maximum allocated IDs
> at
> org.datanucleus.api.jdo.NucleusJDOHelper.getJDOExceptionForNucleusException(NucleusJDOHelper.java:488)
> at
> org.datanucleus.api.jdo.JDOPersistenceManager.jdoMakePersistent(JDOPersistenceManager.java:736)
> at
> org.datanucleus.api.jdo.JDOPersistenceManager.makePersistent(JDOPersistenceManager.java:756)
>
>
>
>
>
>
>
> On Thursday, April 4, 2013 3:37:36 PM UTC+8, GoSharp Lite wrote:
>

> > *Issue 9110:*

[GoSharp Lite]

The code is a simple datastore.put(entity). I'm getting close to find the problem. The kind which gives "Exceeded maximum allocated IDs" only has 1483 entities, but the last entity id=9223259787550119662. This is almost 2^63, which is the limit. I have been using this kind since 2010, it seems the ID generator might be root cause of this error. 

[GoSharp Lite]

I found another kind which gives "Exceeded maximum allocated IDs". This kind only has 2545 entities. Looking at the id sequence, at around 1223 entity id=6070550, the next entity id=9223259787545785651 and increasing. The id generator is behaving strangely.

[GoSharp Lite]

I have a kind which shows the time of id jump as shown below.
id=6045690,             2011-11-17 03:24:34.576000
id=9223259787545788651, 2011-11-18 16:09:36.499000

[GoSharp Lite]

Another kind shows the id jump at about the same time.
id=6071550,             2011-11-18 06:00:31.469000
id=9223259787545787652, 2011-11-18 15:51:32.743000

[Barry Hunter]

This thread

https://groups.google.com/forum/?fromgroups=#!topic/google-appengine/r7L2mH3VzLw

mentions they where going to change the id allocation online. 

Maybe that is now causing issue?

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[GoSharp Lite]

Kinds in my app with key generated by myself still function well. Kinds which I let datastore generate key automatically all has "Exceeded maximum allocated IDs" problem now.

[GoSharp Lite]

The time of id large jump is interesting. 2011/11 was when GAE exited beta.

[GoSharp Lite]

Instead of letting datastore to generate id automatically, I am now generating id for most of my kinds. Luckily several important kinds do not rely on automatic id generation. My app is back online. Is my app the only one experiencing this scary issue?