Jumbune
  1. Jumbune
  2. JUM-74

Debugger fails for large data on CDH5 cluster

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.4.0
    • Fix Version/s: None
    • Component/s: flow debugger
    • Labels:
      None

      Description

      Debugger fails for large data sets on CDH5 cluster.


      2014-12-19 12:21:11,059 ERROR [pool-7-thread-1][DebugProcessor] LogAnalyser Failed !!!
      java.util.concurrent.ExecutionException: java.lang.NullPointerException
      at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:252) ~[?:1.7.0_17]
      at java.util.concurrent.FutureTask.get(FutureTask.java:111) ~[?:1.7.0_17]
      at org.jumbune.debugger.log.processing.LogAnalyzerUtil.processLogs(LogAnalyzerUtil.java:182) ~[jumbune-debugger-1.4.0.jar:?]
      at org.jumbune.execution.processor.DebugProcessor.execute(DebugProcessor.java:114) [jumbune-exec-1.4.0.jar:?]
      at org.jumbune.execution.processor.BaseProcessor.process(BaseProcessor.java:103) [jumbune-exec-1.4.0.jar:?]
      at org.jumbune.execution.service.HttpExecutorService$Handler.run(HttpExecutorService.java:188) [jumbune-exec-1.4.0.jar:?]
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [?:1.7.0_17]
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [?:1.7.0_17]
      at java.lang.Thread.run(Thread.java:722) [?:1.7.0_17]
      Caused by: java.lang.NullPointerException
      at org.jumbune.debugger.log.processing.LogAnalyzer.addInstanceMap(LogAnalyzer.java:402) ~[jumbune-debugger-1.4.0.jar:?]
      at org.jumbune.debugger.log.processing.LogAnalyzer.addNodeMap(LogAnalyzer.java:351) ~[jumbune-debugger-1.4.0.jar:?]
      at org.jumbune.debugger.log.processing.LogAnalyzer.addMapReduceMap(LogAnalyzer.java:300) ~[jumbune-debugger-1.4.0.jar:?]
      at org.jumbune.debugger.log.processing.LogAnalyzer.addJobMap(LogAnalyzer.java:252) ~[jumbune-debugger-1.4.0.jar:?]
      at org.jumbune.debugger.log.processing.LogAnalyzer.processLine(LogAnalyzer.java:201) ~[jumbune-debugger-1.4.0.jar:?]
      at org.jumbune.debugger.log.processing.LogAnalyzer.analyzeLogs(LogAnalyzer.java:124) ~[jumbune-debugger-1.4.0.jar:?]
      at org.jumbune.debugger.log.processing.LogAnalyzerCallable.call(LogAnalyzerCallable.java:49) ~[jumbune-debugger-1.4.0.jar:?]
      at org.jumbune.debugger.log.processing.LogAnalyzerCallable.call(LogAnalyzerCallable.java:14) ~[jumbune-debugger-1.4.0.jar:?]
      at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) ~[?:1.7.0_17]
      at java.util.concurrent.FutureTask.run(FutureTask.java:166) ~[?:1.7.0_17]
      ... 3 more
      2014-12-19 12:21:11,061 INFO [pool-7-thread-1][DebugProcessor] Exited from [Debug] Processor...

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Vivek Shivhare
            Reporter:
            Mahesh Nair
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: