[
https://issues.apache.org/jira/browse/SLIDER-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595869#comment-15595869
]
Manoj Samel edited comment on SLIDER-1169 at 10/21/16 6:04 PM:
---------------------------------------------------------------
Hi [~gsaha], I applied the patch to version 0.80 and it had addressed the
quorum issue
One question - The patch change only one java file AbstractActionArgs.java.
After the change, the build created new slider-core-0.80.0-incubating.jar and
new slider-agent.tar.gz. The tar slider-agent.tar.gz seem to contain only
python files so not sure why the patch would rebuild slider-agent.tar.gz.
I have tested patch by deploying only the new slider-core-0.80.0-incubating.jar
on existing .80 cluster; do the new slider-agent.tar.gz should also be deployed
?
was (Author: manojsamel):
Hi [~gsaha], I applied the patch to version 0.80 and it had addressed the
quorum issue
One question - The patch change only one java file AbstractActionArgs.java.
After the change, the build created new slider-core-0.80.0-incubating.jar and
new slider-agent.tar.gz. The tar slider-agent.tar.gz seem to contain only
python files so not sure why the patch would rebuild slider-agent.tar.gz.
I have tested but deploying only the new slider-core-0.80.0-incubating.jar on
existing cluster; do the new slider-agent.tar.gz should also be deployed ?
> Slider not honoring zookeeper quorum values passed
> --------------------------------------------------
>
> Key: SLIDER-1169
> URL: https://issues.apache.org/jira/browse/SLIDER-1169
> Project: Slider
> Issue Type: Bug
> Components: appmaster
> Affects Versions: Slider 0.91
> Environment: RHEL-6 (64 Bit)
> Reporter: Sandeep Nemuri
> Assignee: Daniel Murnane
> Priority: Critical
> Fix For: Slider 1.0.0
>
> Attachments: SLIDER-1169.patch
>
>
> *PROBLEM* :
> Customer has created a Slider App by passing zookeeper quorum using below
> command :
> {code}
> slider create test --template appConfig.json --resources resources.json
> --zkhosts
> sandy234new1.hwxblr.com:2181,sandy234new3.hwxblr.com:2181,sandy234new2.hwxblr.com:2181
> {code}
> Below is the application log, which show us that it only picks the 1st
> zookeeper.
> {code}
> 2016-09-15 15:44:29,052 [main] INFO appmaster.SliderAppMaster - Loading
> slider-server.xml at
> file:/hadoop/yarn/local/usercache/root/appcache/application_1473930641993_0005/container_e04_1473930641993_0005_01_000001/confdir/slider-server.xml
> 2016-09-15 15:44:29,077 [main] INFO appmaster.SliderAppMaster - AM
> configuration:
> hadoop.registry.zk.quorum=sandy234new1.hwxblr.com:2181
> hadoop.registry.zk.root=/registry
> yarn.resourcemanager.scheduler.address=0.0.0.0:8030
> {code}
> *BUSINESS IMPACT* : Slider throws exceptions when 1st zookeeper goes down
> (Since it only picks 1st zookeeper) and this is impacting the AM.
> *STEPS TO REPRODUCE*:
> Launch a Hbase app using step 1 & 2.
> 1) slider create test --template appConfig.json --resources resources.json
> --zkhosts
> sandy234new1.hwxblr.com:2181,sandy234new3.hwxblr.com:2181,sandy234new2.hwxblr.com:2181
> This will launch a application in RM.
> From the RM UI --> application -> logs
> first line will be as below :
> {code}
> 2016-09-15 15:44:29,052 [main] INFO appmaster.SliderAppMaster - Loading
> slider-server.xml at
> file:/hadoop/yarn/local/usercache/root/appcache/application_1473930641993_0005/container_e04_1473930641993_0005_01_000001/confdir/slider-server.xml
> 2016-09-15 15:44:29,077 [main] INFO appmaster.SliderAppMaster - AM
> configuration:
> hadoop.registry.zk.quorum=sandy234new1.hwxblr.com:2181
> hadoop.registry.zk.root=/registry
> yarn.resourcemanager.scheduler.address=0.0.0.0:8030
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
