Hi there,
I am a MapReduce rookie, so I have a few questions to ask (sorry if they
are silly questions):
- What is the maximum input processing rate?
- The docs say:
- The aggregate number of entities processed per second by all
mappers. Used to prevent large
Never mind, I just found the announcement of the migration to stack
overflow,
Any replies are still appreciated though.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
I also found this which helps a lot:
http://stackoverflow.com/questions/5494251/how-fast-is-google-app-engine-mapreduce
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
Hi, I am running a small map reduce job over only 474 entities (as a test
on my server).
It appears that immediately (despite the fact all my quota should be
replenished now) I am reaching my task queue quota:
/mapreduce/mapperCallback 200 541ms 0kb AppEngine-Google;
Solved.
The jobs were put into a default task que which must have been in
paused status from the go. The jobs are now un-paused and it seems to be
going through them nicely.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view
Solved.
The jobs were put into a default task queue which must have been in
paused status from the go. The jobs are now un-paused and it seems to be
going through them nicely.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To
Hi there,
I have been attempting to copy entities to another application and they
have all seemed to copy correctly. However, the queue still has 83 tasks
(which is the same number as the kinds I copied, so a task for each kind).
The final 83 tasks are no longer making progress and the
Well it is typical that I would go to lunch and the tasks in the queue have
gone.
I'm not sure what happened, but I'm sure I can still run my Mapper over the
entities to test it.
Thanks,
Mark
--
You received this message because you are subscribed to the Google Groups
Google App Engine for
Hi, I have recently created a new application to copy entities to from an
older application.
I have done this in order to test my map reduce jobs safely as I have seem
to be un-able to get it working properly LOCALLY. (see:
Hi there,
I have been following Ikai's blog (which I have found to be most useful, so
thanks):
http://ikaisays.com/2010/07/09/using-the-java-mapper-framework-for-app-engine/
It seems I have set things up properly with web.xml / mapreduce.xml my
mapper class. However, there is a problem.
Oh, I also see:
Status ViewID
NameActivityStart time Time
elapsedControl
... and my task queue for mapreduce:
mapreduce http://192.168.0.56:8080/_ah/admin/taskqueue?queueName=mapreduce
5.0/s100
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
I can remove the Jobs from the datastore and get rid of them that way, but
this does not explain why my Jobs get stuck in RUNNING state and it never
hits the break points in my Mapper class.
I must have set something up slightly wrong, but I can't think what. Here
is my xml:
configurations
Hi there,
I am currently finding myself having to MapReduce over a lot of entities. I
was just wondering if it is possible to MapReduce only over a specific
index ( e.g. get all data for users that are in the following index:
userID(ASC), userName(ASC), userAge(DESC) )
I hope this makes
Sorry, the title of the post is meant to be written as:
Merging older entities with entities that were created into an entity group.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
Sorry, the title of the post is meant to be written as:
Merging older entities with entities that were created into an entity group.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
I understand that I will not have a delay in the case of using ancestor
queries.
This is what I mean: (maybe I failed to make it clear).
The problem we have is when you create a new entity (without using ancestor
queries) and redirect the view to a list of the entities after creation,
you may
I understand that I will not have a delay in the case of using ancestor
queries.
This is what I mean: (maybe I failed to make it clear).
The problem we have is when you create a new entity (without using ancestor
queries) and redirect the view to a list of the entities after creation,
you may
Thanks for the reply Ikai, that was the information I needed.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine-java/-/85UIicBcxZQJ.
To post to
Hi,
I have been doing a lot of reading on Ancestor queries because we are
currently trying to transfer from Master / Slave to the High Replication
datastore.
We have noticed while testing on the HRDS, that sometimes when adding an
entity and redirecting the view to show that entity (or maybe
Basically I have gone through my datastore persist-able classes and have
annotated properties that I never need to query on like this:
@Extension(vendorName=datanucleus, key=gae.unindexed, value=true)
private Long random;
I needed to test whether or not JDO removed the index when I changed the
21 matches
Mail list logo
