HelloWorld example in distributed mode

[Stephen Varey]

I have recently downloaded Tigon and built 0.3.0-SNAPSHOT

I can run the HelloWorld example in standalone mode - no problem

When I run in distributed mode I get this error... I have no idea what the problem is

hadoop@srv ~/tigon/tigon/tigon-examples/HelloWorld/target $ run_distributed.sh maverick001:2181 tigon

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/hadoop/tigon/tigon/tigon-distribution/target/sdk/tigon-sdk-0.3.0-SNAPSHOT/lib/ch.qos.logback.logback-classic-1.0.9.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/hadoop/ecosystem/hbase-0.98.9-hadoop2/lib/slf4j-log4j12-1.6.4.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
Tigon Distributed Client
2015-02-08 14:46:03,053 - INFO  [main:c.c.t.g.LocationRuntimeModule$HDFSLocationModule@85] - HDFS namespace is /tigon
2015-02-08 14:46:03,345 - WARN  [main:o.a.h.u.NativeCodeLoader@62] - Unable to load native-hadoop library for your platform... using builtin-java classes where applicable

tigon> start /home/hadoop/tigon/tigon/tigon-examples/HelloWorld/target/HelloWorld-0.3.0-SNAPSHOT.jar  co.cask.tigon.helloworld.HelloWorldFlow
Error: Chunk [co.cask.tigon.helloworld.HelloWorldFlow] is not a valid entry

[parth]

Hey Stephen,

Firstly, thanks for trying out Tigon!

What seems to be the problem is that you have two spaces between the jar-path and the className - so the CLI attempts to parse the className as a runtime argument and fails. Could you try it again with only one space between the arguments?

If that works, i'd leave the JIRA issue open so we can use it to make the CLI more robust.

Let us know if you have any other questions.

Parth

[Stephen Varey]

Thanks for the prompt reply
Got a bit further but it doesn't look like its running
Just been in the following state for the last hour


hadoop@srv ~/tigon/tigon/bin $ ./run_distributed.sh maverick001:2181 tmp

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/hadoop/tigon/tigon/tigon-distribution/target/sdk/tigon-sdk-0.3.0-SNAPSHOT/lib/ch.qos.logback.logback-classic-1.0.9.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/hadoop/ecosystem/hbase-0.98.9-hadoop2/lib/slf4j-log4j12-1.6.4.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
Tigon Distributed Client

2015-02-09 12:44:46,646 - INFO  [main:c.c.t.g.LocationRuntimeModule$HDFSLocationModule@85] - HDFS namespace is /tmp
2015-02-09 12:44:47,210 - WARN  [main:o.a.h.u.NativeCodeLoader@62] - Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
tigon> start /home/hadoop/runnablejars/HelloWorldFlow.jar ha001.co.cask.tigon.helloworld.HelloWorldFlow
2015-02-09 12:45:19,501 - INFO  [main:c.c.t.f.DeployClient@173] - Created deployedJar at file:/tmp/1423482284537-0/ha001.co.cask.tigon.helloworld.HelloWorldFlow.580186b6-7aae-4a2f-bb04-8ec086713d6b.jar
2015-02-09 12:45:19,502 - INFO  [main:c.c.t.f.DeployClient@143] - Deploy Jar location : file:/tmp/1423482284537-0/ha001.co.cask.tigon.helloworld.HelloWorldFlow.580186b6-7aae-4a2f-bb04-8ec086713d6b.jar
2015-02-09 12:45:23,029 - INFO  [main:c.c.t.i.a.r.d.DistributedFlowProgramRunner@78] - Configuring flowlets queues
2015-02-09 12:45:23,549 - INFO  [main:c.c.t.i.a.r.f.FlowUtils@96] - Queue config for queue:///HelloWorld/HelloWorld/generator/queue : {-5715281355696782671=1}



When I log to another shell I get another error..


hadoop@srv ~/tigon/tigon/bin $ ./run_distributed.sh maverick001:2181 tmp

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/hadoop/tigon/tigon/tigon-distribution/target/sdk/tigon-sdk-0.3.0-SNAPSHOT/lib/ch.qos.logback.logback-classic-1.0.9.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/hadoop/ecosystem/hbase-0.98.9-hadoop2/lib/slf4j-log4j12-1.6.4.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
Tigon Distributed Client

2015-02-09 13:28:48,402 - INFO  [main:c.c.t.g.LocationRuntimeModule$HDFSLocationModule@85] - HDFS namespace is /tmp
2015-02-09 13:28:48,916 - WARN  [main:o.a.h.u.NativeCodeLoader@62] - Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
tigon> checklogs HelloWorld
Error: null

tigon> checklogs
Error: null

tigon> checklogs
Error: null

tigon>

[parth]

Hey Stephen,

When you started the flow you should also have seen a couple more lines similar to: 

2015-02-09 18:19:01,062 - INFO  [main:c.c.t.i.a.r.d.DistributedFlowProgramRunner@82] - Launching distributed flow: co.cask.tigon.helloworld.HelloWorldFlow:HelloWorld

2015-02-09 18:19:21,505 - INFO  [ STARTING:c.c.t.i.a.r.d.AbstractTwillProgramController$1@76] - Twill program running: co.cask.tigon.helloworld.HelloWorldFlow c7ab8097-c83a-4206-8c8d-a30239fa9d7c

2015-02-09 18:19:21,505 - INFO  [ STARTING:c.c.t.i.a.r.AbstractProgramController@201] - Program started: co.cask.tigon.helloworld.HelloWorldFlow c7ab8097-c83a-4206-8c8d-a30239fa9d7c

Assuming those showed up and you just missed copying them in the email, the correct command to show the output is "showlogs <name>". 

Let me know if you see the expected output with that.

[Stephen Varey]

Didnt see that
and now a few hours later got this...

2015-02-09 14:15:06,086 - WARN  [main:o.a.h.h.c.ClientScanner@464] - scanner failed to close. Exception follows: org.apache.hadoop.hbase.client.RetriesExhaustedException: Failed after attempts=35, exceptions:
Mon Feb 09 13:31:15 CET 2015, org.apache.hadoop.hbase.client.RpcRetryingCaller@389bc2d3, java.io.IOException: Failed to find location, tableName=hbase:meta, row=tmp.system.queue.HelloWorld.HelloWorld,,, reload=false
Mon Feb 09 13:32:25 CET 2015, org.apache.hadoop.hbase.client.RpcRetryingCaller@389bc2d3, java.io.IOException: Failed to find location, tableName=hbase:meta, row=tmp.system.queue.HelloWorld.HelloWorld,,, reload=true
Mon Feb 09 13:33:35 CET 2015, org.apache.hadoop.hbase.client.RpcRetryingCaller@389bc2d3, java.io.IOException: Failed to find location, tableName=hbase:meta, row=tmp.system.queue.HelloWorld.HelloWorld,,, reload=true
Mon Feb 09 13:34:45 CET 2015, org.apache.hadoop.hbase.client.RpcRetryingCaller@389bc2d3, java.io.IOException: Failed to find location, tableName=hbase:meta, row=tmp.system.queue.HelloWorld.HelloWorld,,, reload=true
Mon Feb 09 13:35:55 CET 2015, org.apache.hadoop.hbase.client.RpcRetryingCaller@389bc2d3, java.io.IOException: Failed to find location, tableName=hbase:meta, row=tmp.system.queue.HelloWorld.HelloWorld,,, reload=true
Mon Feb 09 13:37:05 CET 2015, org.apache.hadoop.hbase.client.RpcRetryingCaller@389bc2d3, java.io.IOException: Failed to find location, tableName=hbase:meta, row=tmp.system.queue.HelloWorld.HelloWorld,,, reload=true
Mon Feb 09 13:38:15 CET 2015, org.apache.hadoop.hbase.client.RpcRetryingCaller@389bc2d3, java.io.IOException: Failed to find location, tableName=hbase:meta, row=tmp.system.queue.HelloWorld.HelloWorld,,, reload=true
Mon Feb 09 13:39:25 CET 2015, org.apache.hadoop.hbase.client.RpcRetryingCaller@389bc2d3, java.io.IOException: Failed to find location, tableName=hbase:meta, row=tmp.system.queue.HelloWorld.HelloWorld,,, reload=true
Mon Feb 09 13:40:35 CET 2015, org.apache.hadoop.hbase.client.RpcRetryingCaller@389bc2d3, java.io.IOException: Failed to find location, tableName=hbase:meta, row=tmp.system.queue.HelloWorld.HelloWorld,,, reload=true
Mon Feb 09 13:41:45 CET 2015, org.apache.hadoop.hbase.client.RpcRetryingCaller@389bc2d3, java.io.IOException: Failed to find location, tableName=hbase:meta, row=tmp.system.queue.HelloWorld.HelloWorld,,, reload=true

On Sunday, February 8, 2015 at 2:57:45 PM UTC+1, Stephen Varey wrote:

[Gokul Gunasekaran]

Hi Stephen,

When the HelloWorld Flow starts, the runtime system will try and create two tables in HBase : ["tigon.system.queue.HelloWorld.HelloWorld", "tigon.system.queue.config”]. 

What is version of HBase in your cluster? Are there security features enabled in HBase?

Thanks,

Gokul

-- 
You received this message because you are subscribed to the Google Groups "Tigon User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tigon-user+...@googlegroups.com.
To post to this group, send email to tigon...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tigon-user/c59d91f7-e48d-4de2-87de-f77f223e2412%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Gokul Gunasekaran]

Hi Stephen,

Do you see any tables created in HBase : ["tigon.system.queue.HelloWorld.HelloWorld", "tigon.system.queue.config”] ?

You can check this by starting HBase shell : hbase shell. And then use the list command to list the tables present.

For security, you can check the HBase configuration UI ( cluster:60010/conf) and check for the property name : hbase.security.authentication. What value does it have?

Thanks,

Gokul

On Feb 9, 2015, at 12:04 PM, Stephen Varey <srv...@gmail.com> wrote:

version hbase-0.98.9

Dont know how to answer security features

--

[Stephen Varey]

there is no such property in hbase-site.xml

On Sunday, February 8, 2015 at 2:57:45 PM UTC+1, Stephen Varey wrote:

[Gokul Gunasekaran]

Hi Stephen,

Thanks for sending the properties in HBase conf. That looks fine. We need to do a little more debugging to figure out why the hbase-client fails to make a connection to the server (and it keeps retrying). 

Can you try and change the log level to DEBUG in the logback.xml (tigon-client/src/main/resources/logback.xml) [Change the following lines (from INFO to DEBUG)]:

<logger name="co.cask.tigon" level="DEBUG”/>

<root level="DEBUG">

Build the SDK again and then try starting the example again.

Thanks,

Gokul

On Feb 10, 2015, at 12:45 AM, Stephen Varey <srv...@gmail.com> wrote:

Here is some output.

I took out redundant retry info.

hadoop@srv ~/tigon/tigon/bin $ ./run_distributed.sh maverick001:2181 tmp

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/hadoop/tigon/tigon/tigon-distribution/target/sdk/tigon-sdk-0.3.0-SNAPSHOT/lib/ch.qos.logback.logback-classic-1.0.9.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/hadoop/ecosystem/hbase-0.98.9-hadoop2/lib/slf4j-log4j12-1.6.4.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
Tigon Distributed Client

2015-02-09 12:44:46,646 - INFO  [main:c.c.t.g.LocationRuntimeModule$HDFSLocationModule@85] - HDFS namespace is /tmp
2015-02-09 12:44:47,210 - WARN  [main:o.a.h.u.NativeCodeLoader@62] - Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
tigon> start /home/hadoop/runnablejars/HelloWorldFlow.jar ha001.co.cask.tigon.helloworld.HelloWorldFlow
2015-02-09 12:45:19,501 - INFO  [main:c.c.t.f.DeployClient@173] - Created deployedJar at file:/tmp/1423482284537-0/ha001.co.cask.tigon.helloworld.HelloWorldFlow.580186b6-7aae-4a2f-bb04-8ec086713d6b.jar
2015-02-09 12:45:19,502 - INFO  [main:c.c.t.f.DeployClient@143] - Deploy Jar location : file:/tmp/1423482284537-0/ha001.co.cask.tigon.helloworld.HelloWorldFlow.580186b6-7aae-4a2f-bb04-8ec086713d6b.jar
2015-02-09 12:45:23,029 - INFO  [main:c.c.t.i.a.r.d.DistributedFlowProgramRunner@78] - Configuring flowlets queues
2015-02-09 12:45:23,549 - INFO  [main:c.c.t.i.a.r.f.FlowUtils@96] - Queue config for queue:///HelloWorld/HelloWorld/generator/queue : {-5715281355696782671=1}

2015-02-09 14:15:06,086 - WARN  [main:o.a.h.h.c.ClientScanner@464] - scanner failed to close. Exception follows: org.apache.hadoop.hbase.client.RetriesExhaustedException: Failed after attempts=35, exceptions:
Mon Feb 09 13:31:15 CET 2015, org.apache.hadoop.hbase.client.RpcRetryingCaller@389bc2d3, java.io.IOException: Failed to find location, tableName=hbase:meta, row=tmp.system.queue.HelloWorld.HelloWorld,,, reload=false
Mon Feb 09 13:32:25 CET 2015, org.apache.hadoop.hbase.client.RpcRetryingCaller@389bc2d3, java.io.IOException: Failed to find location, tableName=hbase:meta, row=tmp.system.queue.HelloWorld.HelloWorld,,, reload=true
Mon Feb 09 13:33:35 CET 2015, org.apache.hadoop.hbase.client.RpcRetryingCaller@389bc2d3, java.io.IOException: Failed to find location, tableName=hbase:meta, row=tmp.system.queue.HelloWorld.HelloWorld,,, reload=true

2015-02-09 14:15:07,273 - ERROR [main:c.c.t.i.a.r.f.FlowUtils@101] - Failed to configure queues

org.apache.hadoop.hbase.client.RetriesExhaustedException: Failed after attempts=35, exceptions:

Mon Feb 09 12:46:25 CET 2015, org.apache.hadoop.hbase.client.RpcRetryingCaller@389bc2d3, java.io.IOException: Failed to find location, tableName=hbase:meta, row=tmp.system.queue.HelloWorld.HelloWorld,,, reload=false
Mon Feb 09 12:47:35 CET 2015, org.apache.hadoop.hbase.client.RpcRetryingCaller@389bc2d3, java.io.IOException: Failed to find location, tableName=hbase:meta, row=tmp.system.queue.HelloWorld.HelloWorld,,, reload=true
Mon Feb 09 12:48:44 CET 2015, org.apache.hadoop.hbase.client.RpcRetryingCaller@389bc2d3, java.io.IOException: Failed to find location, tableName=hbase:meta, row=tmp.system.queue.HelloWorld.HelloWorld,,, reload=true

    at org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithRetries(RpcRetryingCaller.java:133) ~[hbase-client-0.98.9-hadoop2.jar:0.98.9-hadoop2]
    at org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithRetries(RpcRetryingCaller.java:93) ~[hbase-client-0.98.9-hadoop2.jar:0.98.9-hadoop2]
    at org.apache.hadoop.hbase.client.ClientScanner.nextScanner(ClientScanner.java:283) ~[hbase-client-0.98.9-hadoop2.jar:0.98.9-hadoop2]
    at org.apache.hadoop.hbase.client.ClientScanner.initializeScannerInConstruction(ClientScanner.java:188) ~[hbase-client-0.98.9-hadoop2.jar:0.98.9-hadoop2]
    at org.apache.hadoop.hbase.client.ClientScanner.<init>(ClientScanner.java:183) ~[hbase-client-0.98.9-hadoop2.jar:0.98.9-hadoop2]
    at org.apache.hadoop.hbase.client.ClientScanner.<init>(ClientScanner.java:110) ~[hbase-client-0.98.9-hadoop2.jar:0.98.9-hadoop2]
    at org.apache.hadoop.hbase.client.HTable.getScanner(HTable.java:771) ~[hbase-client-0.98.9-hadoop2.jar:0.98.9-hadoop2]
    at org.apache.hadoop.hbase.catalog.MetaReader.fullScan(MetaReader.java:542) ~[hbase-client-0.98.9-hadoop2.jar:0.98.9-hadoop2]
    at org.apache.hadoop.hbase.catalog.MetaReader.tableExists(MetaReader.java:310) ~[hbase-client-0.98.9-hadoop2.jar:0.98.9-hadoop2]
    at org.apache.hadoop.hbase.client.HBaseAdmin.tableExists(HBaseAdmin.java:307) ~[hbase-client-0.98.9-hadoop2.jar:0.98.9-hadoop2]
    at org.apache.hadoop.hbase.client.HBaseAdmin.tableExists(HBaseAdmin.java:321) ~[hbase-client-0.98.9-hadoop2.jar:0.98.9-hadoop2]
    at co.cask.tigon.data.transaction.queue.hbase.HBaseQueueAdmin.exists(HBaseQueueAdmin.java:208) ~[co.cask.tigon.tigon-queue-0.3.0-SNAPSHOT.jar:na]
    at co.cask.tigon.data.transaction.queue.hbase.HBaseQueueAdmin.configureGroups(HBaseQueueAdmin.java:432) ~[co.cask.tigon.tigon-queue-0.3.0-SNAPSHOT.jar:na]
    at co.cask.tigon.internal.app.runtime.flow.FlowUtils.configureQueue(FlowUtils.java:97) ~[co.cask.tigon.tigon-flow-0.3.0-SNAPSHOT.jar:na]
    at co.cask.tigon.internal.app.runtime.distributed.DistributedFlowProgramRunner.launch(DistributedFlowProgramRunner.java:79) [co.cask.tigon.tigon-flow-0.3.0-SNAPSHOT.jar:na]
    at co.cask.tigon.internal.app.runtime.distributed.AbstractDistributedProgramRunner.run(AbstractDistributedProgramRunner.java:111) [co.cask.tigon.tigon-flow-0.3.0-SNAPSHOT.jar:na]
    at co.cask.tigon.flow.DeployClient.startFlow(DeployClient.java:152) [co.cask.tigon.tigon-flow-0.3.0-SNAPSHOT.jar:na]
    at co.cask.tigon.cli.DistributedFlowOperations.startFlow(DistributedFlowOperations.java:105) [co.cask.tigon.tigon-client-0.3.0-SNAPSHOT.jar:na]
    at co.cask.tigon.cli.commands.StartCommand.startFlow(StartCommand.java:58) [co.cask.tigon.tigon-client-0.3.0-SNAPSHOT.jar:na]
    at co.cask.tigon.cli.commands.StartCommand.execute(StartCommand.java:46) [co.cask.tigon.tigon-client-0.3.0-SNAPSHOT.jar:na]
    at co.cask.common.cli.CLI.execute(CLI.java:125) [co.cask.common.common-cli-0.1.1.jar:na]
    at co.cask.common.cli.CLI.startInteractiveMode(CLI.java:158) [co.cask.common.common-cli-0.1.1.jar:na]
    at co.cask.tigon.cli.commands.TigonCLI.start(TigonCLI.java:114) [co.cask.tigon.tigon-client-0.3.0-SNAPSHOT.jar:na]
    at co.cask.tigon.DistributedMain.startUp(DistributedMain.java:146) [co.cask.tigon.tigon-client-0.3.0-SNAPSHOT.jar:na]
    at co.cask.tigon.DistributedMain.main(DistributedMain.java:114) [co.cask.tigon.tigon-client-0.3.0-SNAPSHOT.jar:na]
Caused by: java.io.IOException: Failed to find location, tableName=hbase:meta, row=tmp.system.queue.HelloWorld.HelloWorld,,, reload=true

--

[Gokul Gunasekaran]

Hi Stephen,

Forgot to mention that this will increase the debug level of the Logs and so if you can send us the logs after changing the log level, that might give us more clues as to what is happening.

Thanks,

Gokul

[Gokul Gunasekaran]

Hi Stephen,

Can you look at the HBase UI : http://clustername:60010

Can you check if there are any dead region servers? 

Another check would be to try and scan the test table you had created via Hbase shell.

> list

> scan ‘tablename'

Also you can take a look at the YARN node manager status through the UI : http://clustername:8088/cluster/nodes.

Let me know what you see in these status checks.

Thanks,

Gokul

On Feb 10, 2015, at 4:27 AM, Stephen Varey <srv...@gmail.com> wrote:

Gokul,

It didn't make any difference . No debug messages only INFO

hadoop@srv ~/tigon/tigon $ find . -name "*.xml" -exec grep -l INFO {} \;
hadoop@srv ~/tigon/tigon $ find . -name "*.xml" -exec grep -l DEBUG {} \;
./tigon-client/src/main/resources/logback.xml
./tigon-client/target/classes/logback.xml
./tigon-sql/src/main/resources/logback.xml
./tigon-sql/target/classes/logback.xml
hadoop@srv ~/tigon/tigon $ vi ./tigon-client/target/classes/logback.xml
hadoop@srv ~/tigon/tigon $ run_distributed.sh maverick001:2181 tmp

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/hadoop/tigon/tigon/tigon-distribution/target/sdk/tigon-sdk-0.3.0-SNAPSHOT/lib/ch.qos.logback.logback-classic-1.0.9.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/hadoop/ecosystem/hbase-0.98.9-hadoop2/lib/slf4j-log4j12-1.6.4.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
Tigon Distributed Client

2015-02-10 13:24:39,120 - INFO  [main:c.c.t.g.LocationRuntimeModule$HDFSLocationModule@85] - HDFS namespace is /tmp
2015-02-10 13:24:39,489 - WARN  [main:o.a.h.u.NativeCodeLoader@62] - Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
tigon> start /home/hadoop/runnablejars/HelloWorldFlow.jar ha001.co.cask.tigon.helloworld.HelloWorldFlow
2015-02-10 13:25:13,747 - INFO  [main:c.c.t.f.DeployClient@173] - Created deployedJar at file:/tmp/1423571077455-0/ha001.co.cask.tigon.helloworld.HelloWorldFlow.d2a69645-7c51-4d60-8b60-40747d1c90e3.jar
2015-02-10 13:25:13,747 - INFO  [main:c.c.t.f.DeployClient@143] - Deploy Jar location : file:/tmp/1423571077455-0/ha001.co.cask.tigon.helloworld.HelloWorldFlow.d2a69645-7c51-4d60-8b60-40747d1c90e3.jar
2015-02-10 13:25:16,441 - INFO  [main:c.c.t.i.a.r.d.DistributedFlowProgramRunner@78] - Configuring flowlets queues
2015-02-10 13:25:16,502 - INFO  [main:c.c.t.i.a.r.f.FlowUtils@96] - Queue config for queue:///HelloWorld/HelloWorld/generator/queue : {-5715281355696782671=1}

--