Hadoop Common
  1. Hadoop Common
  2. HADOOP-5908

ArithmeticException in heartbeats with zero map jobs

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.20.1
    • Component/s: None
    • Labels:
      None
    • Hadoop Flags:
      Reviewed
    1. HADOOP-5908-v3.0.patch
      6 kB
      Amar Kamat
    2. HADOOP-5908-v3.1.patch
      8 kB
      Amar Kamat
    3. HADOOP-5908-v3.2.20.patch
      8 kB
      Robert Chansler
    4. HADOOP-5908-v3.2.patch
      8 kB
      Amar Kamat
    5. HADOOP-5908-v3.3.patch
      8 kB
      Amar Kamat
    6. HADOOP-5908-v3.3-branch20.patch
      8 kB
      Amar Kamat

      Activity

      Hide
      Vinod Kumar Vavilapalli added a comment -

      This issue was found by Ramya while testing HADOOP-5850. Statement by Ramya on that JIRA follows:

      With the above fix, when a job (writing to DFS) with 0 maps and >0 reduces is submitted, the cluster hangs completely.
      The TT logs show "INFO org.apache.hadoop.mapred.TaskTracker: Resending 'status' to <jt>' with reponseId 'ID" infinitely and the JT throws java.io.IOException: java.lang.ArithmeticException forever.
      Below is the stacktrace:

      2009-05-25 08:13:00,124 INFO org.apache.hadoop.ipc.Server: IPC Server handler 37 on <portno>, call heartbeat(org.apache.hadoop.mapred.TaskTrackerStatus@14d128c, false, false, true, 3231) from <ip>:<port> error: java.io.IOException:
      java.lang.ArithmeticException: / by zero
      java.io.IOException: java.lang.ArithmeticException: / by zero
      at org.apache.hadoop.mapred.ResourceEstimator.getEstimatedMapOutputSize(ResourceEstimator.java:85)
      at org.apache.hadoop.mapred.JobInProgress.findNewMapTask(JobInProgress.java:1729)
      at org.apache.hadoop.mapred.JobInProgress.obtainNewMapTask(JobInProgress.java:978)
      at org.apache.hadoop.mapred.CapacityTaskScheduler$MapSchedulingMgr.obtainNewTask(CapacityTaskScheduler.java:572)
      at org.apache.hadoop.mapred.CapacityTaskScheduler$TaskSchedulingMgr.getTaskFromQueue(CapacityTaskScheduler.java:418)
      at org.apache.hadoop.mapred.CapacityTaskScheduler$TaskSchedulingMgr.assignTasks(CapacityTaskScheduler.java:498)
      at org.apache.hadoop.mapred.CapacityTaskScheduler$TaskSchedulingMgr.access$500(CapacityTaskScheduler.java:277)
      at org.apache.hadoop.mapred.CapacityTaskScheduler.assignTasks(CapacityTaskScheduler.java:977)
      at org.apache.hadoop.mapred.JobTracker.heartbeat(JobTracker.java:2605)
      at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:597)
      at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:508)
      at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:959)
      at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:955)
      at java.security.AccessController.doPrivileged(Native Method)
      at javax.security.auth.Subject.doAs(Subject.java:396)
      at org.apache.hadoop.ipc.Server$Handler.run(Server.java:953)

      In such a case, all the jobs hang infinitely without progressing and the cluster is completely down.
      This problem is solved only when the no-map job is killed. Once the job is killed the cluster is back running and the other jobs proceed smoothly.

      The TT logs show "INFO org.apache.hadoop.mapred.TaskTracker: Resending 'status' to <jt>' with reponseId 'ID" infinitely and the JT throws java.io.IOException: java.lang.ArithmeticException forever. Below is the stacktrace:

      2009-05-25 08:13:00,124 INFO org.apache.hadoop.ipc.Server: IPC Server handler 37 on <portno>, call heartbeat(org.apache.hadoop.mapred.TaskTrackerStatus@14d128c, false, false, true, 3231) from <ip>:<port> error: java.io.IOException:
      java.lang.ArithmeticException: / by zero
      java.io.IOException: java.lang.ArithmeticException: / by zero
      at org.apache.hadoop.mapred.ResourceEstimator.getEstimatedMapOutputSize(ResourceEstimator.java:85)
      at org.apache.hadoop.mapred.JobInProgress.findNewMapTask(JobInProgress.java:1729)
      at org.apache.hadoop.mapred.JobInProgress.obtainNewMapTask(JobInProgress.java:978)
      at org.apache.hadoop.mapred.CapacityTaskScheduler$MapSchedulingMgr.obtainNewTask(CapacityTaskScheduler.java:572)
      at org.apache.hadoop.mapred.CapacityTaskScheduler$TaskSchedulingMgr.getTaskFromQueue(CapacityTaskScheduler.java:418)
      at org.apache.hadoop.mapred.CapacityTaskScheduler$TaskSchedulingMgr.assignTasks(CapacityTaskScheduler.java:498)
      at org.apache.hadoop.mapred.CapacityTaskScheduler$TaskSchedulingMgr.access$500(CapacityTaskScheduler.java:277)
      at org.apache.hadoop.mapred.CapacityTaskScheduler.assignTasks(CapacityTaskScheduler.java:977)
      at org.apache.hadoop.mapred.JobTracker.heartbeat(JobTracker.java:2605)
      at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:597)
      at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:508)
      at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:959)
      at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:955)
      at java.security.AccessController.doPrivileged(Native Method)
      at javax.security.auth.Subject.doAs(Subject.java:396)
      at org.apache.hadoop.ipc.Server$Handler.run(Server.java:953)

      In such a case, all the jobs hang infinitely without progressing and the cluster is completely down. This problem is solved only when the no-map job is killed. Once the job is killed the cluster is back running and the other jobs proceed smoothly.

      Show
      Vinod Kumar Vavilapalli added a comment - This issue was found by Ramya while testing HADOOP-5850 . Statement by Ramya on that JIRA follows: With the above fix, when a job (writing to DFS) with 0 maps and >0 reduces is submitted, the cluster hangs completely. The TT logs show "INFO org.apache.hadoop.mapred.TaskTracker: Resending 'status' to <jt>' with reponseId 'ID" infinitely and the JT throws java.io.IOException: java.lang.ArithmeticException forever. Below is the stacktrace: 2009-05-25 08:13:00,124 INFO org.apache.hadoop.ipc.Server: IPC Server handler 37 on <portno>, call heartbeat(org.apache.hadoop.mapred.TaskTrackerStatus@14d128c, false, false, true, 3231) from <ip>:<port> error: java.io.IOException: java.lang.ArithmeticException: / by zero java.io.IOException: java.lang.ArithmeticException: / by zero at org.apache.hadoop.mapred.ResourceEstimator.getEstimatedMapOutputSize(ResourceEstimator.java:85) at org.apache.hadoop.mapred.JobInProgress.findNewMapTask(JobInProgress.java:1729) at org.apache.hadoop.mapred.JobInProgress.obtainNewMapTask(JobInProgress.java:978) at org.apache.hadoop.mapred.CapacityTaskScheduler$MapSchedulingMgr.obtainNewTask(CapacityTaskScheduler.java:572) at org.apache.hadoop.mapred.CapacityTaskScheduler$TaskSchedulingMgr.getTaskFromQueue(CapacityTaskScheduler.java:418) at org.apache.hadoop.mapred.CapacityTaskScheduler$TaskSchedulingMgr.assignTasks(CapacityTaskScheduler.java:498) at org.apache.hadoop.mapred.CapacityTaskScheduler$TaskSchedulingMgr.access$500(CapacityTaskScheduler.java:277) at org.apache.hadoop.mapred.CapacityTaskScheduler.assignTasks(CapacityTaskScheduler.java:977) at org.apache.hadoop.mapred.JobTracker.heartbeat(JobTracker.java:2605) at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:508) at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:959) at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:955) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:396) at org.apache.hadoop.ipc.Server$Handler.run(Server.java:953) In such a case, all the jobs hang infinitely without progressing and the cluster is completely down. This problem is solved only when the no-map job is killed. Once the job is killed the cluster is back running and the other jobs proceed smoothly. The TT logs show "INFO org.apache.hadoop.mapred.TaskTracker: Resending 'status' to <jt>' with reponseId 'ID" infinitely and the JT throws java.io.IOException: java.lang.ArithmeticException forever. Below is the stacktrace: 2009-05-25 08:13:00,124 INFO org.apache.hadoop.ipc.Server: IPC Server handler 37 on <portno>, call heartbeat(org.apache.hadoop.mapred.TaskTrackerStatus@14d128c, false, false, true, 3231) from <ip>:<port> error: java.io.IOException: java.lang.ArithmeticException: / by zero java.io.IOException: java.lang.ArithmeticException: / by zero at org.apache.hadoop.mapred.ResourceEstimator.getEstimatedMapOutputSize(ResourceEstimator.java:85) at org.apache.hadoop.mapred.JobInProgress.findNewMapTask(JobInProgress.java:1729) at org.apache.hadoop.mapred.JobInProgress.obtainNewMapTask(JobInProgress.java:978) at org.apache.hadoop.mapred.CapacityTaskScheduler$MapSchedulingMgr.obtainNewTask(CapacityTaskScheduler.java:572) at org.apache.hadoop.mapred.CapacityTaskScheduler$TaskSchedulingMgr.getTaskFromQueue(CapacityTaskScheduler.java:418) at org.apache.hadoop.mapred.CapacityTaskScheduler$TaskSchedulingMgr.assignTasks(CapacityTaskScheduler.java:498) at org.apache.hadoop.mapred.CapacityTaskScheduler$TaskSchedulingMgr.access$500(CapacityTaskScheduler.java:277) at org.apache.hadoop.mapred.CapacityTaskScheduler.assignTasks(CapacityTaskScheduler.java:977) at org.apache.hadoop.mapred.JobTracker.heartbeat(JobTracker.java:2605) at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:508) at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:959) at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:955) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:396) at org.apache.hadoop.ipc.Server$Handler.run(Server.java:953) In such a case, all the jobs hang infinitely without progressing and the cluster is completely down. This problem is solved only when the no-map job is killed. Once the job is killed the cluster is back running and the other jobs proceed smoothly.
      Hide
      Vinod Kumar Vavilapalli added a comment -

      This situation occurs if scheduler is invoked and it calls job.obtainNewMapTask() while the job-clean-up task of this job is still running. Discussed with this Devaraj who concurs that obtainNewMapTask()/obtainNewReduceTask() should return immediately, doing nothing, when job-cleanup is running.

      Show
      Vinod Kumar Vavilapalli added a comment - This situation occurs if scheduler is invoked and it calls job.obtainNewMapTask() while the job-clean-up task of this job is still running. Discussed with this Devaraj who concurs that obtainNewMapTask()/obtainNewReduceTask() should return immediately, doing nothing, when job-cleanup is running.
      Hide
      Amar Kamat added a comment -

      Attaching a patch that guards the maps value to be non-zero in denominator. Result of test-patch

      [exec] +1 overall.  
           [exec] 
           [exec]     +1 @author.  The patch does not contain any @author tags.
           [exec] 
           [exec]     +1 tests included.  The patch appears to include 6 new or modified tests.
           [exec] 
           [exec]     +1 javadoc.  The javadoc tool did not generate any warning messages.
           [exec] 
           [exec]     +1 javac.  The applied patch does not increase the total number of javac compiler warnings.
           [exec] 
           [exec]     +1 findbugs.  The patch does not introduce any new Findbugs warnings.
           [exec] 
           [exec]     +1 Eclipse classpath. The patch retains Eclipse classpath integrity.
           [exec] 
           [exec]     +1 release audit.  The applied patch does not increase the total number of release audit warnings
      

      Verified that jip.desiredMap() is checked for non-zero value before using it in denominator.

      Testing in progress.

      Show
      Amar Kamat added a comment - Attaching a patch that guards the maps value to be non-zero in denominator. Result of test-patch [exec] +1 overall. [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] +1 tests included. The patch appears to include 6 new or modified tests. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] +1 findbugs. The patch does not introduce any new Findbugs warnings. [exec] [exec] +1 Eclipse classpath. The patch retains Eclipse classpath integrity. [exec] [exec] +1 release audit. The applied patch does not increase the total number of release audit warnings Verified that jip.desiredMap() is checked for non-zero value before using it in denominator. Testing in progress.
      Hide
      Amar Kamat added a comment -

      ant test passed on my box.

      Show
      Amar Kamat added a comment - ant test passed on my box.
      Hide
      Ramya Sunil added a comment -

      With the above patch, observed NPE in heartbeats with zero map jobs.
      Below is the stacktrace

      java.lang.NullPointerException
      java.io.IOException: java.lang.NullPointerException
              at org.apache.hadoop.mapred.JobInProgress.findNewMapTask(JobInProgress.java:1777)
              at org.apache.hadoop.mapred.JobInProgress.obtainNewMapTask(JobInProgress.java:982)
              at org.apache.hadoop.mapred.CapacityTaskScheduler$MapSchedulingMgr.obtainNewTask(CapacityTaskScheduler.java:572)
              at org.apache.hadoop.mapred.CapacityTaskScheduler$TaskSchedulingMgr.getTaskFromQueue(CapacityTaskScheduler.java:418)
              at org.apache.hadoop.mapred.CapacityTaskScheduler$TaskSchedulingMgr.assignTasks(CapacityTaskScheduler.java:498)
              at org.apache.hadoop.mapred.CapacityTaskScheduler$TaskSchedulingMgr.access$500(CapacityTaskScheduler.java:277)
              at org.apache.hadoop.mapred.CapacityTaskScheduler.assignTasks(CapacityTaskScheduler.java:977)
              at org.apache.hadoop.mapred.JobTracker.heartbeat(JobTracker.java:2605)
              at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              at java.lang.reflect.Method.invoke(Method.java:597)
              at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:508)
              at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:959)
              at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:955)
              at java.security.AccessController.doPrivileged(Native Method)
              at javax.security.auth.Subject.doAs(Subject.java:396)
              at org.apache.hadoop.ipc.Server$Handler.run(Server.java:953)
      
      Show
      Ramya Sunil added a comment - With the above patch, observed NPE in heartbeats with zero map jobs. Below is the stacktrace java.lang.NullPointerException java.io.IOException: java.lang.NullPointerException at org.apache.hadoop.mapred.JobInProgress.findNewMapTask(JobInProgress.java:1777) at org.apache.hadoop.mapred.JobInProgress.obtainNewMapTask(JobInProgress.java:982) at org.apache.hadoop.mapred.CapacityTaskScheduler$MapSchedulingMgr.obtainNewTask(CapacityTaskScheduler.java:572) at org.apache.hadoop.mapred.CapacityTaskScheduler$TaskSchedulingMgr.getTaskFromQueue(CapacityTaskScheduler.java:418) at org.apache.hadoop.mapred.CapacityTaskScheduler$TaskSchedulingMgr.assignTasks(CapacityTaskScheduler.java:498) at org.apache.hadoop.mapred.CapacityTaskScheduler$TaskSchedulingMgr.access$500(CapacityTaskScheduler.java:277) at org.apache.hadoop.mapred.CapacityTaskScheduler.assignTasks(CapacityTaskScheduler.java:977) at org.apache.hadoop.mapred.JobTracker.heartbeat(JobTracker.java:2605) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:508) at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:959) at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:955) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:396) at org.apache.hadoop.ipc.Server$Handler.run(Server.java:953)
      Hide
      Amar Kamat added a comment -

      Attaching a new patch that short circuits the scheduling of maps/reducers = 0. Testing in progress.

      Show
      Amar Kamat added a comment - Attaching a new patch that short circuits the scheduling of maps/reducers = 0. Testing in progress.
      Hide
      Amar Kamat added a comment -

      Result of test-patch

      [exec] +1 overall.  
           [exec] 
           [exec]     +1 @author.  The patch does not contain any @author tags.
           [exec] 
           [exec]     +1 tests included.  The patch appears to include 6 new or modified tests.
           [exec] 
           [exec]     +1 javadoc.  The javadoc tool did not generate any warning messages.
           [exec] 
           [exec]     +1 javac.  The applied patch does not increase the total number of javac compiler warnings.
           [exec] 
           [exec]     +1 findbugs.  The patch does not introduce any new Findbugs warnings.
           [exec] 
           [exec]     +1 Eclipse classpath. The patch retains Eclipse classpath integrity.
           [exec] 
           [exec]     +1 release audit.  The applied patch does not increase the total number of release audit warnings.
      

      Running ant test now.

      Show
      Amar Kamat added a comment - Result of test-patch [exec] +1 overall. [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] +1 tests included. The patch appears to include 6 new or modified tests. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] +1 findbugs. The patch does not introduce any new Findbugs warnings. [exec] [exec] +1 Eclipse classpath. The patch retains Eclipse classpath integrity. [exec] [exec] +1 release audit. The applied patch does not increase the total number of release audit warnings. Running ant test now.
      Hide
      Amar Kamat added a comment -

      ant tests passed on my box.

      Show
      Amar Kamat added a comment - ant tests passed on my box.
      Hide
      Amar Kamat added a comment -

      Incorporated offline changes suggested by Devaraj. Result of test-patch

      [exec] +1 overall.  
           [exec] 
           [exec]     +1 @author.  The patch does not contain any @author tags.
           [exec] 
           [exec]     +1 tests included.  The patch appears to include 9 new or modified tests.
           [exec] 
           [exec]     +1 javadoc.  The javadoc tool did not generate any warning messages.
           [exec] 
           [exec]     +1 javac.  The applied patch does not increase the total number of javac compiler warnings.
           [exec] 
           [exec]     +1 findbugs.  The patch does not introduce any new Findbugs warnings.
           [exec] 
           [exec]     +1 Eclipse classpath. The patch retains Eclipse classpath integrity.
           [exec] 
           [exec]     +1 release audit.  The applied patch does not increase the total number of release audit warnings.
      

      Running ant test now

      Show
      Amar Kamat added a comment - Incorporated offline changes suggested by Devaraj. Result of test-patch [exec] +1 overall. [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] +1 tests included. The patch appears to include 9 new or modified tests. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] +1 findbugs. The patch does not introduce any new Findbugs warnings. [exec] [exec] +1 Eclipse classpath. The patch retains Eclipse classpath integrity. [exec] [exec] +1 release audit. The applied patch does not increase the total number of release audit warnings. Running ant test now
      Hide
      Amar Kamat added a comment -

      Attaching a correct patch.

      Show
      Amar Kamat added a comment - Attaching a correct patch.
      Hide
      Amar Kamat added a comment -

      test-patch and ant tests passed on my box.

      Show
      Amar Kamat added a comment - test-patch and ant tests passed on my box.
      Hide
      Devaraj Das added a comment -

      The testcase has a problem - the cleanup task is meant to block for a long time but it looks like it might not in the current implemented.

      Show
      Devaraj Das added a comment - The testcase has a problem - the cleanup task is meant to block for a long time but it looks like it might not in the current implemented.
      Hide
      Amar Kamat added a comment -

      Attaching a patch incorporating Devaraj's comments. Result of test-patch

       [exec] +1 overall.  
           [exec] 
           [exec]     +1 @author.  The patch does not contain any @author tags.
           [exec] 
           [exec]     +1 tests included.  The patch appears to include 6 new or modified tests.
           [exec] 
           [exec]     +1 javadoc.  The javadoc tool did not generate any warning messages.
           [exec] 
           [exec]     +1 javac.  The applied patch does not increase the total number of javac compiler warnings.
           [exec] 
           [exec]     +1 findbugs.  The patch does not introduce any new Findbugs warnings.
           [exec] 
           [exec]     +1 Eclipse classpath. The patch retains Eclipse classpath integrity.
           [exec] 
           [exec]     +1 release audit.  The applied patch does not increase the total number of release audit warnings.
      

      Ant test passed on my box.

      Show
      Amar Kamat added a comment - Attaching a patch incorporating Devaraj's comments. Result of test-patch [exec] +1 overall. [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] +1 tests included. The patch appears to include 6 new or modified tests. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] +1 findbugs. The patch does not introduce any new Findbugs warnings. [exec] [exec] +1 Eclipse classpath. The patch retains Eclipse classpath integrity. [exec] [exec] +1 release audit. The applied patch does not increase the total number of release audit warnings. Ant test passed on my box.
      Hide
      Amar Kamat added a comment -

      Attaching a patch for 0.20 branch.

      Show
      Amar Kamat added a comment - Attaching a patch for 0.20 branch.
      Hide
      Devaraj Das added a comment -

      I just committed this. Thanks, Amar!

      Show
      Devaraj Das added a comment - I just committed this. Thanks, Amar!
      Hide
      Robert Chansler added a comment -

      Attached alternate 0.20 patch that is not to be committed to the branch.

      Show
      Robert Chansler added a comment - Attached alternate 0.20 patch that is not to be committed to the branch.

        People

        • Assignee:
          Amar Kamat
          Reporter:
          Vinod Kumar Vavilapalli
        • Votes:
          0 Vote for this issue
          Watchers:
          3 Start watching this issue

          Dates

          • Created:
            Updated:
            Resolved:

            Development