Hey Shekar,
To contribute to that page (or any docs), do the following:
1. Open a JIRA defining the issue (that you intend to fix) with the docs.
2. Check out samza's code base.
3. Change the docs (located in the 'docs' folder). They are markdown
formatted docs.
4. Run a `git diff` from the root
Chris,
I think I am comfortable now to add couple of steps to the multi node setup.
II am guessing I need some privileges to contribute to
http://samza.apache.org/learn/tutorials/0.7.0/run-in-multi-node-yarn.html
(need a jira ticket and privilege to add context and close it as well)
- Shekar
On
After adding classpath to yarn-site.xml, I found that the jars that were
created for argos (extension of Samza) was not part of the tar.gz file that
was exposed to Http request. I changed the post install script on rpm to
expose that.
I see that the 2 nodes are showing up on rm. We are testing red
Hey Shekar,
Awesome, thanks! Would love to get any doc updates that would be useful.
Curious: what was wrong?
Cheers,
Chris
On Fri, Mar 13, 2015 at 1:00 PM, Shekar Tippur wrote:
> Thanks for your help Chris. Got it to work now. I will test my case and
> documentation further. I can edit the S
Thanks for your help Chris. Got it to work now. I will test my case and
documentation further. I can edit the Samza documentation to reflect any
changes.
- Shekar
On Thu, Mar 12, 2015 at 5:19 PM, Chris Riccomini
wrote:
> Hey Shekar,
>
> Yes, this is definitely a classpath issue. The pastebin yo
Hey Shekar,
Yes, this is definitely a classpath issue. The pastebin you sent does not
include any of the samza-core/samza-yarn/scala JARs. This is rather
strange, since you said you put the JARs in this path:
/home/hadoop/hadoop-2.5.2/share/hadoop/hdfs/lib/
And I do see *other* JARs listed wit
Chris,
Made some progress.
By adding yarn.application.classpath to yarn-site.xml, I am no longer
getting class not found error. However, I am getting a different error:
Application application_1426204312971_0001 failed 2 times due to AM
Container for appattempt_1426204312971_0001_02 exited w
Chris - Here it is.
http://pastebin.com/c3e21Hzf
- Shekar
On Thu, Mar 12, 2015 at 10:58 AM, Chris Riccomini
wrote:
> This is the line that I'm interested in:
>
> STARTUP_MSG: classpath
>
> On Thu, Mar 12, 2015 at 10:55 AM, Chris Riccomini
> wrote:
>
> > Hey Shekar,
> >
> > Could you pa
This is the line that I'm interested in:
STARTUP_MSG: classpath
On Thu, Mar 12, 2015 at 10:55 AM, Chris Riccomini
wrote:
> Hey Shekar,
>
> Could you paste the full log on pastebin? It really seems like something's
> missing from the classpath. If samza-yarn is there, it should be able to
Hey Shekar,
Could you paste the full log on pastebin? It really seems like something's
missing from the classpath. If samza-yarn is there, it should be able to
see that file. I think the full log has a dump of the classpath. If it
doesn't, could you paste the line where the YARN NM is starting up,
I think all these jars are in place (Under
$HADOOP_YARN_HOME/share/hadoop/hdfs/lib)
- Shekar
On Thu, Mar 12, 2015 at 9:36 AM, Chris Riccomini
wrote:
> Hey Shekar,
>
> You need that samza-yarn file on your RM/NM's classpath, along with scala.
> We missed this in the docs, and are tracking the is
Hey Shekar,
You need that samza-yarn file on your RM/NM's classpath, along with scala.
We missed this in the docs, and are tracking the issue here:
https://issues.apache.org/jira/browse/SAMZA-456
You'll also need samza-core in the classpath, based on the discussion on
SAMZA-456. Sorry about th
Here is the corresponding log:
2015-03-11 20:43:09,665 INFO [AsyncDispatcher event handler]
localizer.LocalizedResource (LocalizedResource.java:handle(203)) - Resource
http://sprfargas102:8000/hello-samza-0.8.0-dist.tar.gz transitioned from
INIT to DOWNLOADING
2015-03-11 20:43:09,665 INFO [Asyn
13 matches
Mail list logo
