Karam Singh added a comment - 07/Feb/12 14:40 Settings for For RM scalability comparison :- GridMix settings were for both Hadoop-0.20.204 and Hadoop-0.23 : gridmix.client.submit.threads=10 gridmix.submit.multiplier=0.01 gridmix.client.pending.queue.depth=100 gridmix.job.type=SLEEPJOB gridmix.sleep.maptask-only= false gridmix.sleep.max-map-time=300000 gridmix.sleep.max-reduce-tim=300000 gridmix.sleep.fake-locations=3 gridmix.distributed-cache-emulation.enable=falseemulation.enable> gridmix.compression-emulation.enable= false From JobHistroy Parsing and GridMix client found that : Runtime (seconds): 2473 GridMix Simulation Time Spent: 41mins 8sec Workflow End: 2046 (From histroy parsing) While looking at GridMix log and JobHistory files : 1. Found that according to gm client last was completed was 12/02/07 08:32:26 INFO gridmix.JobMonitor: GRIDMIX000029 job_1328600848949_1182) success. Whereas the EndTime of Job is : 1328602818684 Tue, 07 Feb 2012 08:20:18 Which means somehow GridMix got Job completion event 12 minutes after the the actual job got completed . 2. Similarly acc. to JobHistory last Jo completed was : job_1328600848949_1162: 1328603121882 Tue, 07 Feb 2012 08:25:21 Whereas according to GridMix client log: 12/02/07 08:32:08 INFO gridmix.JobMonitor: GRIDMIX000029 (job_1328600848949_1162) success Which again means GridMix got job completion event nearly 7 minutes after the actual job got finished. Whereas this problem does not exists with Hadoop-0.20.204 Seems that, Somehow in Hadoop-0.23, GridMix is getting job completion events long after the actual job getting completed

Arun C Murthy added a comment - 07/Feb/12 19:26 This looks like a bug in GridMix. Amar, can you please take a look? Thanks.

Amol Kekre added a comment - 16/Feb/12 15:28 pls close this jira. RM scalability now matches .204

Vinod Kumar Vavilapalli added a comment - 16/Feb/12 21:27 Thanks for the update Amol. Closing this as fixed, couple of the tickets tracked under MAPREDUCE-3561 automatically addressed this I suppose.