Uploaded image for project: 'Samza'
  1. Samza
  2. SAMZA-895

wikipediafeed is not working in 4 node cluster node

    Details

    • Type: Bug
    • Status: Open
    • Priority: Critical
    • Resolution: Unresolved
    • Affects Version/s: 0.10.0
    • Fix Version/s: 0.10.0
    • Component/s: hello-samza
    • Labels:
      None
    • Environment:

      4 node cluster setup

    • Flags:
      Important

      Description

      In standardlone hello samza is working but when come's to 4 node cluster same is not working (only wikipediafeed is not working )

      2016-03-14 20:11:01 ContainerUtil [INFO] Starting container ID 0 using package path http://192.168.1.193:8000/target/hello-samza-0.10.0-dist.tar.gz
      2016-03-14 20:11:01 ContainerUtil [INFO] starting container http://192.168.1.193:8000/target/hello-samza-0.10.0-dist.tar.gz Container: [ContainerId: container_1457929705180_0002_01_000006, NodeId: slave1:54616, NodeHttpAddress: slave1:8042, Resource: <memory:1024, vCores:1>, Priority: 0, Token: Token

      { kind: ContainerToken, service: 192.168.1.190:54616 }

      , ]

      {SAMZA_CONTAINER_ID=0, SAMZA_COORDINATOR_URL=http://slave2:43971/, JAVA_OPTS=}

      export SAMZA_LOG_DIR=<LOG_DIR> && ln -sfn <LOG_DIR> logs && exec ./__package/bin/run-container.sh 1>logs/stdout 2>logs/stderr
      2016-03-14 20:11:01 ContainerManagementProtocolProxy [INFO] Opening proxy : slave1:54616
      2016-03-14 20:11:01 ContainerUtil [INFO] Claimed container ID 0 for container container_1457929705180_0002_01_000006 on node slave1 (http://slave1:8042/node/containerlogs/container_1457929705180_0002_01_000006).
      2016-03-14 20:11:01 ContainerUtil [INFO] Started container ID 0
      2016-03-14 20:11:01 ContainerRequestState [INFO] No more pending requests in queue.
      2016-03-14 20:11:02 JobCoordinator$ [INFO] New task Partition 0 is being assigned changelog partition 0.
      2016-03-14 20:11:02 TaskConfig [INFO] No task.name.grouper.factory configuration, using 'org.apache.samza.container.grouper.task.GroupByContainerCountFactory'
      2016-03-14 20:11:02 CoordinatorStreamSystemConsumer [INFO] Bootstrapping configuration from coordinator stream.
      2016-03-14 20:11:02 LocalityManager [INFO] Read locality for container 0:

      {jmx-url=service:jmx:rmi://localhost:46459/jndi/rmi://localhost:46458/jmxrmi, host=slave1, jmx-tunneling-url=service:jmx:rmi://slave1:46459/jndi/rmi://slave1:46458/jmxrmi}

      2016-03-14 20:11:02 LocalityManager [INFO] Read locality for container 0:

      {jmx-url=service:jmx:rmi://localhost:35284/jndi/rmi://localhost:35283/jmxrmi, host=slave1, jmx-tunneling-url=service:jmx:rmi://slave1:35284/jndi/rmi://slave1:35283/jmxrmi}

      2016-03-14 20:11:02 LocalityManager [INFO] Read locality for container 0:

      {jmx-url=service:jmx:rmi://localhost:49723/jndi/rmi://localhost:49722/jmxrmi, host=slave1, jmx-tunneling-url=service:jmx:rmi://slave1:49723/jndi/rmi://slave1:49722/jmxrmi}

      2016-03-14 20:11:02 LocalityManager [INFO] Read locality for container 0:

      {jmx-url=service:jmx:rmi://localhost:50472/jndi/rmi://localhost:50471/jmxrmi, host=slave1, jmx-tunneling-url=service:jmx:rmi://slave1:50472/jndi/rmi://slave1:50471/jmxrmi}

      2016-03-14 20:11:04 SamzaTaskManager [INFO] Container failed for some reason. Let's start it again
      2016-03-14 20:11:04 SamzaTaskManager [INFO] Container container_1457929705180_0002_01_000006 failed with exit code 1 - Exception from container-launch.
      Container id: container_1457929705180_0002_01_000006
      Exit code: 1
      Stack trace: ExitCodeException exitCode=1:
      at org.apache.hadoop.util.Shell.runCommand(Shell.java:545)
      at org.apache.hadoop.util.Shell.run(Shell.java:456)
      at org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:722)
      at org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.launchContainer(DefaultContainerExecutor.java:212)
      at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:302)
      at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:82)
      at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
      at java.lang.Thread.run(Thread.java:745)

      Container exited with a non-zero exit code 1

      2016-03-14 20:11:04 CoordinatorStreamSystemConsumer [INFO] Bootstrapping configuration from coordinator stream.
      2016-03-14 20:11:04 LocalityManager [INFO] Read locality for container 0:

      {jmx-url=service:jmx:rmi://localhost:46459/jndi/rmi://localhost:46458/jmxrmi, host=slave1, jmx-tunneling-url=service:jmx:rmi://slave1:46459/jndi/rmi://slave1:46458/jmxrmi}

      2016-03-14 20:11:04 LocalityManager [INFO] Read locality for container 0:

      {jmx-url=service:jmx:rmi://localhost:35284/jndi/rmi://localhost:35283/jmxrmi, host=slave1, jmx-tunneling-url=service:jmx:rmi://slave1:35284/jndi/rmi://slave1:35283/jmxrmi}

      2016-03-14 20:11:04 LocalityManager [INFO] Read locality for container 0:

      {jmx-url=service:jmx:rmi://localhost:49723/jndi/rmi://localhost:49722/jmxrmi, host=slave1, jmx-tunneling-url=service:jmx:rmi://slave1:49723/jndi/rmi://slave1:49722/jmxrmi}

      2016-03-14 20:11:04 LocalityManager [INFO] Read locality for container 0:

      {jmx-url=service:jmx:rmi://localhost:50472/jndi/rmi://localhost:50471/jmxrmi, host=slave1, jmx-tunneling-url=service:jmx:rmi://slave1:50472/jndi/rmi://slave1:50471/jmxrmi}

      2016-03-14 20:11:04 LocalityManager [INFO] Read locality for container 0:

      {jmx-url=service:jmx:rmi://localhost:44770/jndi/rmi://localhost:44769/jmxrmi, host=slave1, jmx-tunneling-url=service:jmx:rmi://slave1:44770/jndi/rmi://slave1:44769/jmxrmi}

      2016-03-14 20:11:04 SamzaTaskManager [INFO] Current fail count for container ID 0 is 5.
      2016-03-14 20:11:04 ContainerRequestState [INFO] Requesting a container for 0 at ANY_HOST
      2016-03-14 20:11:04 RackResolver [INFO] Resolved ANY_HOST to /default-rack
      2016-03-14 20:11:08 RackResolver [INFO] Resolved ANY_HOST to /default-rack

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              naredrak0411@gmail.com Narendra Kadari
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:

                Time Tracking

                Estimated:
                Original Estimate - 96h
                96h
                Remaining:
                Remaining Estimate - 96h
                96h
                Logged:
                Time Spent - Not Specified
                Not Specified