[jira] [Commented] (SLIDER-633) Slider should support invocation via Oozie

2014-11-18 Thread Lee Yang (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLIDER-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217390#comment-14217390
 ] 

Lee Yang commented on SLIDER-633:
-

Sorry, I had been trying quite a few things in the process of getting this to 
work, and it could just be that this isn't required.  Unfortunately, I've been 
unable to test this today due to some grid downtime on my end. 

> Slider should support invocation via Oozie
> --
>
> Key: SLIDER-633
> URL: https://issues.apache.org/jira/browse/SLIDER-633
> Project: Slider
>  Issue Type: Improvement
>Affects Versions: Slider 0.50
>Reporter: Lee Yang
> Attachments: fix_oozie_launch.patch
>
>
> In a secure Hadoop installation, when attempting to launch a slider 
> application via an Oozie shell-action, I see the following exception:
> {noformat}
> Stdoutput org.apache.hadoop.ipc.RemoteException(java.io.IOException): 
> Delegation Token can be issued only with kerberos or web authentication
> Stdoutput at 
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getDelegationToken(FSNamesystem.java:6757)
> Stdoutput at 
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.getDelegationToken(NameNodeRpcServer.java:499)
> Stdoutput at 
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.getDelegationToken(ClientNamenodeProtocolServerSideTranslatorPB.java:921)
> Stdoutput at 
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
> Stdoutput at 
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:585)
> Stdoutput at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:928)
> Stdoutput at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2013)
> Stdoutput at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2009)
> Stdoutput at java.security.AccessController.doPrivileged(Native Method)
> Stdoutput at javax.security.auth.Subject.doAs(Subject.java:415)
> Stdoutput at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1637)
> Stdoutput at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2007)
> Stdoutput 
> Stdoutput at org.apache.hadoop.ipc.Client.call(Client.java:1411)
> Stdoutput at org.apache.hadoop.ipc.Client.call(Client.java:1364)
> Stdoutput at 
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:206)
> Stdoutput at com.sun.proxy.$Proxy17.getDelegationToken(Unknown Source)
> Stdoutput at 
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.getDelegationToken(ClientNamenodeProtocolTranslatorPB.java:864)
> Stdoutput at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> Stdoutput at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> Stdoutput at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Stdoutput at java.lang.reflect.Method.invoke(Method.java:601)
> Stdoutput at 
> org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:187)
> Stdoutput at 
> org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:102)
> Stdoutput at com.sun.proxy.$Proxy18.getDelegationToken(Unknown Source)
> Stdoutput at 
> org.apache.hadoop.hdfs.DFSClient.getDelegationToken(DFSClient.java:947)
> Stdoutput at 
> org.apache.hadoop.hdfs.DistributedFileSystem.getDelegationToken(DistributedFileSystem.java:1305)
> Stdoutput at 
> org.apache.hadoop.fs.FileSystem.collectDelegationTokens(FileSystem.java:527)
> Stdoutput at 
> org.apache.hadoop.fs.FileSystem.addDelegationTokens(FileSystem.java:505)
> Stdoutput at 
> org.apache.slider.core.launch.AppMasterLauncher.addSecurityTokens(AppMasterLauncher.java:209)
> Stdoutput at 
> org.apache.slider.core.launch.AppMasterLauncher.completeAppMasterLaunch(AppMasterLauncher.java:183)
> Stdoutput at 
> org.apache.slider.core.launch.AppMasterLauncher.submitApplication(AppMasterLauncher.java:214)
> Stdoutput at 
> org.apache.slider.client.SliderClient.launchApplication(SliderClient.java:1127)
> Stdoutput at 
> org.apache.slider.client.SliderClient.startCluster(SliderClient.java:771)
> Stdoutput at 
> org.apache.slider.client.SliderClient.actionCreate(SliderClient.java:515)
> Stdoutput at 
> org.apache.slider.client.SliderClient.runService(SliderClient.java:295)
> Stdoutput at 
> org.apache.slider.core.main.ServiceLauncher.launchService(ServiceLauncher.java:186)
> Stdoutput at 
> org.apache.slider.core.main.ServiceLauncher.launchServiceRobustly(ServiceLauncher.java:471)
> Stdoutput at 
> org.apache.slider.core.main.Serv

[jira] [Commented] (SLIDER-642) apache rat not found in mvn repos

2014-11-18 Thread Josh Elser (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLIDER-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217186#comment-14217186
 ] 

Josh Elser commented on SLIDER-642:
---

[~ste...@apache.org], try {{mvn org.apache.rat.apache-rat:check}} instead.

Alternatively, if you add the following to your {{$HOME/.m2/settings.xml}}, 
{{mvn apache-rat:check}} should start working:

{code}

org.apache.rat

{code}

> apache rat not found in mvn repos
> -
>
> Key: SLIDER-642
> URL: https://issues.apache.org/jira/browse/SLIDER-642
> Project: Slider
>  Issue Type: Bug
>  Components: build
>Affects Versions: Slider 0.60
>Reporter: Steve Loughran
>Priority: Minor
>
> {code}
> $ mvn apache-rat:check
> {code}
> leads to
> {code}
> [ERROR] No plugin found for prefix 'apache-rat' in the current project and in 
> the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available 
> from the repositories [local (/Users/stevel/.m2/repository), ASF Staging 
> (https://repository.apache.org/content/groups/staging/), central 
> (http://repo.maven.apache.org/maven2)] -> [Help 1]
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLIDER-641) two slider-agent tarballs in lib dir

2014-11-18 Thread Sumit Mohanty (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLIDER-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sumit Mohanty updated SLIDER-641:
-
Sprint: Slider December #1

> two slider-agent tarballs in lib dir
> 
>
> Key: SLIDER-641
> URL: https://issues.apache.org/jira/browse/SLIDER-641
> Project: Slider
>  Issue Type: Bug
>  Components: build
>Affects Versions: Slider 0.60
>Reporter: Steve Loughran
>
> full builds create two versions of the agent tarball, one with a version 
> number, one without



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLIDER-651) intermittent failure of TestStandaloneAgentAM on windows

2014-11-18 Thread Sumit Mohanty (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLIDER-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sumit Mohanty updated SLIDER-651:
-
Sprint: Slider December #1

> intermittent failure of TestStandaloneAgentAM on windows
> 
>
> Key: SLIDER-651
> URL: https://issues.apache.org/jira/browse/SLIDER-651
> Project: Slider
>  Issue Type: Bug
>  Components: test
>Affects Versions: Slider 0.60
> Environment: windows
>Reporter: Steve Loughran
>Priority: Minor
>
> {{TestStandaloneAgentAM}} failing intermittently saying the port allocated is 
> out of the range of requested ports.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLIDER-642) apache rat not found in mvn repos

2014-11-18 Thread Sumit Mohanty (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLIDER-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sumit Mohanty updated SLIDER-642:
-
Sprint: Slider December #1

> apache rat not found in mvn repos
> -
>
> Key: SLIDER-642
> URL: https://issues.apache.org/jira/browse/SLIDER-642
> Project: Slider
>  Issue Type: Bug
>  Components: build
>Affects Versions: Slider 0.60
>Reporter: Steve Loughran
>Priority: Minor
>
> {code}
> $ mvn apache-rat:check
> {code}
> leads to
> {code}
> [ERROR] No plugin found for prefix 'apache-rat' in the current project and in 
> the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available 
> from the repositories [local (/Users/stevel/.m2/repository), ASF Staging 
> (https://repository.apache.org/content/groups/staging/), central 
> (http://repo.maven.apache.org/maven2)] -> [Help 1]
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLIDER-648) Support component level properties

2014-11-18 Thread Sumit Mohanty (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLIDER-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sumit Mohanty updated SLIDER-648:
-
Sprint: Slider December #1

> Support component level properties
> --
>
> Key: SLIDER-648
> URL: https://issues.apache.org/jira/browse/SLIDER-648
> Project: Slider
>  Issue Type: Improvement
>Reporter: Siyuan Hua
>
> Nowadays I could define properties like this 
> global:{
>  "site.COMPONENT1.mykey" : "myvalue"
> }
> That's better to define component properties in component section like this:
> components": {
> "COMPONENT1": {
>   *"mykey": "myvalue"*
> },



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLIDER-649) TestStandaloneAMRestart fails intermittently on windows

2014-11-18 Thread Sumit Mohanty (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLIDER-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sumit Mohanty updated SLIDER-649:
-
Sprint: Slider December #1

> TestStandaloneAMRestart fails intermittently on windows
> ---
>
> Key: SLIDER-649
> URL: https://issues.apache.org/jira/browse/SLIDER-649
> Project: Slider
>  Issue Type: Bug
>Reporter: Jonathan Maron
>
> Failure is probably do invalid client interactions during AM lifecycle.  For 
> time time being will try to address these with longer sleep times.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLIDER-532) Design Slider to spawn Docker container

2014-11-18 Thread Sumit Mohanty (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLIDER-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sumit Mohanty updated SLIDER-532:
-
Sprint: Slider December #1

> Design Slider to spawn Docker container
> ---
>
> Key: SLIDER-532
> URL: https://issues.apache.org/jira/browse/SLIDER-532
> Project: Slider
>  Issue Type: Improvement
>Reporter: thomas liu
>Assignee: thomas liu
> Fix For: Slider 2.0.0
>
>
> Review Docker documentation
> Summarize Slider agent requirement
> Review how YARN help spawn docker container
> Design how Slider spawn Docker container
> Have it reviewed by the team



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Application configuration page is outdated?

2014-11-18 Thread Gour Saha 
Given you moved to 0.60 it would be a good idea to start with the default
file in this branch - ./app-packages/hbase/appConfig-default.json

The site documentation is getting updated as we speak.

-Gour

On Tue, Nov 18, 2014 at 2:14 PM, hsy...@gmail.com  wrote:

> I just figure out:
>
> config_types is changed to system_configs
>
> Or you can have configFile in metainfo.xml and create configuration
> folder with xml or env configuration files in it
>
>
> On Tue, Nov 18, 2014 at 2:04 PM, Sumit Mohanty 
> wrote:
>
> > Sharing the metainfo.xml, appConfig.json, and resources.json should be
> > enough.
> >
> > -Sumit
> >
> > On Tue, Nov 18, 2014 at 2:00 PM, Sumit Mohanty  >
> > wrote:
> >
> > > Is it possible for you to share the application package? I can browse
> > > through it to see what needs to change.
> > >
> > > On Tue, Nov 18, 2014 at 1:48 PM, hsy...@gmail.com 
> > > wrote:
> > >
> > >> Hi guys,
> > >>
> > >> I just switch from 40 to 60 and I found the application configuration
> > >> doesn't work any more.
> > >>
> > >>
> >
> http://slider.incubator.apache.org/docs/slider_specs/application_instance_configuration.html
> > >>
> > >> For example :
> > >>
> > >> {
> > >>   "schema" : "http://example.org/specification/v2.0.0";,
> > >>   "metadata" : {
> > >>   },
> > >>   "global" : {
> > >>   "config_types": "core-site,hdfs-site,hbase-site",
> > >>
> > >>   "java_home": "/usr/jdk64/jdk1.7.0_45",
> > >>   "package_list": "files/hbase-0.96.1-hadoop2-bin.tar",
> > >>   "create.default.zookeeper.node": "true"
> > >>
> > >>   "site.global.app_user": "yarn",
> > >>   "site.global.app_log_dir": "${AGENT_LOG_ROOT}/app/log",
> > >>   "site.global.app_pid_dir": "${AGENT_WORK_ROOT}/app/run",
> > >>   "site.global.security_enabled": "false",
> > >>
> > >>   "site.hbase-site.hbase.hstore.flush.retries.number": "120",
> > >>   "site.hbase-site.hbase.client.keyvalue.maxsize": "10485760",
> > >>   "site.hbase-site.hbase.hstore.compactionThreshold": "3",
> > >>   "site.hbase-site.hbase.rootdir": "${NN_URI}/apps/hbase/data",
> > >>   "site.hbase-site.hbase.tmp.dir":
> > "${AGENT_WORK_ROOT}/work/app/tmp",
> > >>   "site.hbase-site.hbase.master.info.port":
> > >> "${HBASE_MASTER.ALLOCATED_PORT}",
> > >>   "site.hbase-site.hbase.regionserver.port": "0",
> > >>   "site.hbase-site.zookeeper.znode.parent": "${DEF_ZK_PATH}",
> > >>
> > >>   "site.core-site.fs.defaultFS": "${NN_URI}",
> > >>   "site.hdfs-site.dfs.namenode.https-address": "${NN_HOST}:50470",
> > >>   "site.hdfs-site.dfs.namenode.http-address": "${NN_HOST}:50070"
> > >>   }
> > >> }
> > >>
> > >>
> > >> I can't get config_types in agent python script anymore. Only global
> > >> properties are set and caught
> > >>
> > >>
> > >>
> > >> Thanks!
> > >>
> > >
> > >
> >
> > --
> > CONFIDENTIALITY NOTICE
> > NOTICE: This message is intended for the use of the individual or entity
> to
> > which it is addressed and may contain information that is confidential,
> > privileged and exempt from disclosure under applicable law. If the reader
> > of this message is not the intended recipient, you are hereby notified
> that
> > any printing, copying, dissemination, distribution, disclosure or
> > forwarding of this communication is strictly prohibited. If you have
> > received this communication in error, please contact the sender
> immediately
> > and delete it from your system. Thank You.
> >
>

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

[jira] [Updated] (SLIDER-469) Slider tool should have a option for flexing up or down by relative numbers

2014-11-18 Thread Sumit Mohanty (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLIDER-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sumit Mohanty updated SLIDER-469:
-
Sprint: Slider December #1

> Slider tool should have a option for flexing up or down by relative numbers
> ---
>
> Key: SLIDER-469
> URL: https://issues.apache.org/jira/browse/SLIDER-469
> Project: Slider
>  Issue Type: Improvement
>  Components: core
>Affects Versions: Slider 0.60
>Reporter: Steve Loughran
> Fix For: Slider 2.0.0
>
>
> reported:
> bq. Currently Slider cli has option of flexing but that option takes total no 
> of instances.
> bq. But instead we should also introduce flex up or down option.
> {code}
> ./slider flex  mycl2 --component MEMCACHED 2
> {code}
> bq. This will increase the memcached containers by 2 [ instead of total two ].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLIDER-549) remove or repurpose FsDelegationTokenMgr

2014-11-18 Thread Sumit Mohanty (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLIDER-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sumit Mohanty updated SLIDER-549:
-
Sprint: Slider December #1

> remove or repurpose FsDelegationTokenMgr
> 
>
> Key: SLIDER-549
> URL: https://issues.apache.org/jira/browse/SLIDER-549
> Project: Slider
>  Issue Type: Bug
>  Components: appmaster, security
>Reporter: Jonathan Maron
>Assignee: Jonathan Maron
> Fix For: Slider 2.0.0
>
>
> Given the switch to keytabs, a token renewing element is no longer required. 
> However, it may be repurposed in the future to manage token related 
> operations.  For the time being make sure its removed from the app master 
> code and tests.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLIDER-618) Keep only one folder for conf

2014-11-18 Thread Sumit Mohanty (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLIDER-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sumit Mohanty updated SLIDER-618:
-
Sprint: Slider December #1

> Keep only one folder for conf
> -
>
> Key: SLIDER-618
> URL: https://issues.apache.org/jira/browse/SLIDER-618
> Project: Slider
>  Issue Type: Bug
>  Components: build
>Affects Versions: Slider 0.50
>Reporter: Sumit Mohanty
> Fix For: Slider 2.0.0
>
>
> There are two folders "conf" and "conf-hdp" that contain default configs for 
> Slider. One gets used during rpm build and another during the build of the 
> binary tarball.
> Both should be merged into one folder.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLIDER-507) Have Agent report its version to AppMaster

2014-11-18 Thread Sumit Mohanty (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLIDER-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sumit Mohanty updated SLIDER-507:
-
Sprint: Slider December #1

> Have Agent report its version to AppMaster
> --
>
> Key: SLIDER-507
> URL: https://issues.apache.org/jira/browse/SLIDER-507
> Project: Slider
>  Issue Type: Bug
>  Components: agent, agent-provider
>Affects Versions: Slider 0.50
>Reporter: Sumit Mohanty
>Assignee: Gour Saha
> Fix For: Slider 2.0.0
>
>
> In preparation for upgrade.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLIDER-617) review conf/ directories in slider-assembly

2014-11-18 Thread Sumit Mohanty (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLIDER-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sumit Mohanty updated SLIDER-617:
-
Sprint: Slider December #1

> review conf/ directories in slider-assembly
> ---
>
> Key: SLIDER-617
> URL: https://issues.apache.org/jira/browse/SLIDER-617
> Project: Slider
>  Issue Type: Test
>Reporter: Steve Loughran
> Fix For: Slider 0.70
>
>
> have a look at the assembly/src/conf dirs and make sure we are happy with them



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLIDER-629) Slider's count of failure threshold may not be accurate or it could be a logging issue

2014-11-18 Thread Sumit Mohanty (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLIDER-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sumit Mohanty updated SLIDER-629:
-
Sprint: Slider December #1

> Slider's count of failure threshold may not be accurate or it could be a 
> logging issue
> --
>
> Key: SLIDER-629
> URL: https://issues.apache.org/jira/browse/SLIDER-629
> Project: Slider
>  Issue Type: Bug
>  Components: appmaster
>Affects Versions: Slider 0.50
>Reporter: Sumit Mohanty
>Assignee: Jonathan Maron
> Fix For: Slider 0.70
>
>
> One of the long running HBase tests failed with the following error:
> {noformat}
> 2014-11-08 01:07:26,407 [AmExecutor-008] ERROR appmaster.SliderAppMaster - 
> Cluster teardown triggered 
> org.apache.slider.core.exceptions.TriggerClusterTeardownException: Unstable 
> Application Instance : - failed with component H   BASE_REGIONSERVER 
> failing 8 times (0 in startup); threshold is 5 - last failure: Failure 
> container_1415341585168_0005_01_08 on host onprem-slider23: 
> http://onprem-slider21:19888/jobhistory/logs/onprem-slider23:45454/contai 
>   ner_1415341585168_0005_01_08/ctx/hadoop^M
> {noformat}
> However, there were total of "9" REGION_SERVERs created.
> {noformat}
> 2014-11-07 16:00:35,346 [AMRM Callback Handler Thread] INFO  state.AppState - 
> Assigning role HBASE_REGIONSERVER to container 
> container_1415341585168_0005_01_02, on onprem-slider25:45454,
> 2014-11-07 16:00:35,347 [AMRM Callback Handler Thread] INFO  state.AppState - 
> Assigning role HBASE_REGIONSERVER to container 
> container_1415341585168_0005_01_05, on onprem-slider24:45454,
> 2014-11-07 16:00:35,347 [AMRM Callback Handler Thread] INFO  state.AppState - 
> Assigning role HBASE_REGIONSERVER to container 
> container_1415341585168_0005_01_07, on onprem-slider22:45454,
> 2014-11-07 16:00:35,347 [AMRM Callback Handler Thread] INFO  state.AppState - 
> Assigning role HBASE_REGIONSERVER to container 
> container_1415341585168_0005_01_08, on onprem-slider23:45454,
> 2014-11-07 23:51:20,040 [AMRM Callback Handler Thread] INFO  state.AppState - 
> Assigning role HBASE_REGIONSERVER to container 
> container_1415341585168_0005_01_09, on onprem-slider22:45454,
> 2014-11-07 23:58:44,810 [AMRM Callback Handler Thread] INFO  state.AppState - 
> Assigning role HBASE_REGIONSERVER to container 
> container_1415341585168_0005_01_13, on onprem-slider24:45454,
> 2014-11-08 00:12:17,804 [AMRM Callback Handler Thread] INFO  state.AppState - 
> Assigning role HBASE_REGIONSERVER to container 
> container_1415341585168_0005_01_15, on onprem-slider22:45454,
> 2014-11-08 00:15:57,373 [AMRM Callback Handler Thread] INFO  state.AppState - 
> Assigning role HBASE_REGIONSERVER to container 
> container_1415341585168_0005_01_18, on onprem-slider25:45454,
> 2014-11-08 01:06:36,771 [AMRM Callback Handler Thread] INFO  state.AppState - 
> Assigning role HBASE_REGIONSERVER to container 
> container_1415341585168_0005_01_20, on onprem-slider25:45454,
> {noformat}
> As the ask was for 4 but 9 were created, obviously there are 5 failures.
> Perhaps its a logging issue. Can we also print the Window - e.g. 5 failures 
> in X minutes or hours.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Application configuration page is outdated?

2014-11-18 Thread hsy...@gmail.com 
I just figure out:

config_types is changed to system_configs

Or you can have configFile in metainfo.xml and create configuration
folder with xml or env configuration files in it


On Tue, Nov 18, 2014 at 2:04 PM, Sumit Mohanty 
wrote:

> Sharing the metainfo.xml, appConfig.json, and resources.json should be
> enough.
>
> -Sumit
>
> On Tue, Nov 18, 2014 at 2:00 PM, Sumit Mohanty 
> wrote:
>
> > Is it possible for you to share the application package? I can browse
> > through it to see what needs to change.
> >
> > On Tue, Nov 18, 2014 at 1:48 PM, hsy...@gmail.com 
> > wrote:
> >
> >> Hi guys,
> >>
> >> I just switch from 40 to 60 and I found the application configuration
> >> doesn't work any more.
> >>
> >>
> http://slider.incubator.apache.org/docs/slider_specs/application_instance_configuration.html
> >>
> >> For example :
> >>
> >> {
> >>   "schema" : "http://example.org/specification/v2.0.0";,
> >>   "metadata" : {
> >>   },
> >>   "global" : {
> >>   "config_types": "core-site,hdfs-site,hbase-site",
> >>
> >>   "java_home": "/usr/jdk64/jdk1.7.0_45",
> >>   "package_list": "files/hbase-0.96.1-hadoop2-bin.tar",
> >>   "create.default.zookeeper.node": "true"
> >>
> >>   "site.global.app_user": "yarn",
> >>   "site.global.app_log_dir": "${AGENT_LOG_ROOT}/app/log",
> >>   "site.global.app_pid_dir": "${AGENT_WORK_ROOT}/app/run",
> >>   "site.global.security_enabled": "false",
> >>
> >>   "site.hbase-site.hbase.hstore.flush.retries.number": "120",
> >>   "site.hbase-site.hbase.client.keyvalue.maxsize": "10485760",
> >>   "site.hbase-site.hbase.hstore.compactionThreshold": "3",
> >>   "site.hbase-site.hbase.rootdir": "${NN_URI}/apps/hbase/data",
> >>   "site.hbase-site.hbase.tmp.dir":
> "${AGENT_WORK_ROOT}/work/app/tmp",
> >>   "site.hbase-site.hbase.master.info.port":
> >> "${HBASE_MASTER.ALLOCATED_PORT}",
> >>   "site.hbase-site.hbase.regionserver.port": "0",
> >>   "site.hbase-site.zookeeper.znode.parent": "${DEF_ZK_PATH}",
> >>
> >>   "site.core-site.fs.defaultFS": "${NN_URI}",
> >>   "site.hdfs-site.dfs.namenode.https-address": "${NN_HOST}:50470",
> >>   "site.hdfs-site.dfs.namenode.http-address": "${NN_HOST}:50070"
> >>   }
> >> }
> >>
> >>
> >> I can't get config_types in agent python script anymore. Only global
> >> properties are set and caught
> >>
> >>
> >>
> >> Thanks!
> >>
> >
> >
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>

Re: Application configuration page is outdated?

2014-11-18 Thread Sumit Mohanty 
Sharing the metainfo.xml, appConfig.json, and resources.json should be
enough.

-Sumit

On Tue, Nov 18, 2014 at 2:00 PM, Sumit Mohanty 
wrote:

> Is it possible for you to share the application package? I can browse
> through it to see what needs to change.
>
> On Tue, Nov 18, 2014 at 1:48 PM, hsy...@gmail.com 
> wrote:
>
>> Hi guys,
>>
>> I just switch from 40 to 60 and I found the application configuration
>> doesn't work any more.
>>
>> http://slider.incubator.apache.org/docs/slider_specs/application_instance_configuration.html
>>
>> For example :
>>
>> {
>>   "schema" : "http://example.org/specification/v2.0.0";,
>>   "metadata" : {
>>   },
>>   "global" : {
>>   "config_types": "core-site,hdfs-site,hbase-site",
>>
>>   "java_home": "/usr/jdk64/jdk1.7.0_45",
>>   "package_list": "files/hbase-0.96.1-hadoop2-bin.tar",
>>   "create.default.zookeeper.node": "true"
>>
>>   "site.global.app_user": "yarn",
>>   "site.global.app_log_dir": "${AGENT_LOG_ROOT}/app/log",
>>   "site.global.app_pid_dir": "${AGENT_WORK_ROOT}/app/run",
>>   "site.global.security_enabled": "false",
>>
>>   "site.hbase-site.hbase.hstore.flush.retries.number": "120",
>>   "site.hbase-site.hbase.client.keyvalue.maxsize": "10485760",
>>   "site.hbase-site.hbase.hstore.compactionThreshold": "3",
>>   "site.hbase-site.hbase.rootdir": "${NN_URI}/apps/hbase/data",
>>   "site.hbase-site.hbase.tmp.dir": "${AGENT_WORK_ROOT}/work/app/tmp",
>>   "site.hbase-site.hbase.master.info.port":
>> "${HBASE_MASTER.ALLOCATED_PORT}",
>>   "site.hbase-site.hbase.regionserver.port": "0",
>>   "site.hbase-site.zookeeper.znode.parent": "${DEF_ZK_PATH}",
>>
>>   "site.core-site.fs.defaultFS": "${NN_URI}",
>>   "site.hdfs-site.dfs.namenode.https-address": "${NN_HOST}:50470",
>>   "site.hdfs-site.dfs.namenode.http-address": "${NN_HOST}:50070"
>>   }
>> }
>>
>>
>> I can't get config_types in agent python script anymore. Only global
>> properties are set and caught
>>
>>
>>
>> Thanks!
>>
>
>

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: Application configuration page is outdated?

2014-11-18 Thread Sumit Mohanty 
Is it possible for you to share the application package? I can browse
through it to see what needs to change.

On Tue, Nov 18, 2014 at 1:48 PM, hsy...@gmail.com  wrote:

> Hi guys,
>
> I just switch from 40 to 60 and I found the application configuration
> doesn't work any more.
>
> http://slider.incubator.apache.org/docs/slider_specs/application_instance_configuration.html
>
> For example :
>
> {
>   "schema" : "http://example.org/specification/v2.0.0";,
>   "metadata" : {
>   },
>   "global" : {
>   "config_types": "core-site,hdfs-site,hbase-site",
>
>   "java_home": "/usr/jdk64/jdk1.7.0_45",
>   "package_list": "files/hbase-0.96.1-hadoop2-bin.tar",
>   "create.default.zookeeper.node": "true"
>
>   "site.global.app_user": "yarn",
>   "site.global.app_log_dir": "${AGENT_LOG_ROOT}/app/log",
>   "site.global.app_pid_dir": "${AGENT_WORK_ROOT}/app/run",
>   "site.global.security_enabled": "false",
>
>   "site.hbase-site.hbase.hstore.flush.retries.number": "120",
>   "site.hbase-site.hbase.client.keyvalue.maxsize": "10485760",
>   "site.hbase-site.hbase.hstore.compactionThreshold": "3",
>   "site.hbase-site.hbase.rootdir": "${NN_URI}/apps/hbase/data",
>   "site.hbase-site.hbase.tmp.dir": "${AGENT_WORK_ROOT}/work/app/tmp",
>   "site.hbase-site.hbase.master.info.port":
> "${HBASE_MASTER.ALLOCATED_PORT}",
>   "site.hbase-site.hbase.regionserver.port": "0",
>   "site.hbase-site.zookeeper.znode.parent": "${DEF_ZK_PATH}",
>
>   "site.core-site.fs.defaultFS": "${NN_URI}",
>   "site.hdfs-site.dfs.namenode.https-address": "${NN_HOST}:50470",
>   "site.hdfs-site.dfs.namenode.http-address": "${NN_HOST}:50070"
>   }
> }
>
>
> I can't get config_types in agent python script anymore. Only global
> properties are set and caught
>
>
>
> Thanks!
>

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Application configuration page is outdated?

2014-11-18 Thread hsy...@gmail.com 
Hi guys,

I just switch from 40 to 60 and I found the application configuration
doesn't work any more.
http://slider.incubator.apache.org/docs/slider_specs/application_instance_configuration.html

For example :

{
  "schema" : "http://example.org/specification/v2.0.0";,
  "metadata" : {
  },
  "global" : {
  "config_types": "core-site,hdfs-site,hbase-site",

  "java_home": "/usr/jdk64/jdk1.7.0_45",
  "package_list": "files/hbase-0.96.1-hadoop2-bin.tar",
  "create.default.zookeeper.node": "true"

  "site.global.app_user": "yarn",
  "site.global.app_log_dir": "${AGENT_LOG_ROOT}/app/log",
  "site.global.app_pid_dir": "${AGENT_WORK_ROOT}/app/run",
  "site.global.security_enabled": "false",

  "site.hbase-site.hbase.hstore.flush.retries.number": "120",
  "site.hbase-site.hbase.client.keyvalue.maxsize": "10485760",
  "site.hbase-site.hbase.hstore.compactionThreshold": "3",
  "site.hbase-site.hbase.rootdir": "${NN_URI}/apps/hbase/data",
  "site.hbase-site.hbase.tmp.dir": "${AGENT_WORK_ROOT}/work/app/tmp",
  "site.hbase-site.hbase.master.info.port":
"${HBASE_MASTER.ALLOCATED_PORT}",
  "site.hbase-site.hbase.regionserver.port": "0",
  "site.hbase-site.zookeeper.znode.parent": "${DEF_ZK_PATH}",

  "site.core-site.fs.defaultFS": "${NN_URI}",
  "site.hdfs-site.dfs.namenode.https-address": "${NN_HOST}:50470",
  "site.hdfs-site.dfs.namenode.http-address": "${NN_HOST}:50070"
  }
}


I can't get config_types in agent python script anymore. Only global
properties are set and caught



Thanks!

Re: slider stop bug?

2014-11-18 Thread hsy...@gmail.com 
I'm using 0.60

On Tue, Nov 18, 2014 at 12:26 PM, Sumit Mohanty 
wrote:

> You can use --force.
>
> Are you using the RC for 0.60 or 0.40?
>
> On Tue, Nov 18, 2014 at 12:00 PM, hsy...@gmail.com 
> wrote:
>
> > If the application is stuck in ACCEPT status, slider stop command doesn't
> > stop the yarn application.
> >
> > I didn't setup the scheduler address correctly so the application stuck
> at
> > ACCEPT status and I couldn't use slider stop to stop the application
> >
> > Best,
> > Siyuan
> >
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>

Re: slider stop bug?

2014-11-18 Thread Sumit Mohanty 
You can use --force.

Are you using the RC for 0.60 or 0.40?

On Tue, Nov 18, 2014 at 12:00 PM, hsy...@gmail.com  wrote:

> If the application is stuck in ACCEPT status, slider stop command doesn't
> stop the yarn application.
>
> I didn't setup the scheduler address correctly so the application stuck at
> ACCEPT status and I couldn't use slider stop to stop the application
>
> Best,
> Siyuan
>

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: slider stop bug?

2014-11-18 Thread Ted Yu 
Did you specify --force ?

You can find explanation for this flag here:
http://slider.incubator.apache.org/docs/manpage.html

On Tue, Nov 18, 2014 at 12:00 PM, hsy...@gmail.com  wrote:

> If the application is stuck in ACCEPT status, slider stop command doesn't
> stop the yarn application.
>
> I didn't setup the scheduler address correctly so the application stuck at
> ACCEPT status and I couldn't use slider stop to stop the application
>
> Best,
> Siyuan
>

slider stop bug?

2014-11-18 Thread hsy...@gmail.com 
If the application is stuck in ACCEPT status, slider stop command doesn't
stop the yarn application.

I didn't setup the scheduler address correctly so the application stuck at
ACCEPT status and I couldn't use slider stop to stop the application

Best,
Siyuan

[jira] [Updated] (SLIDER-657) Introduce --force switch for slider destroy command

2014-11-18 Thread Gour Saha (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLIDER-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gour Saha updated SLIDER-657:
-
Description: 
Slider destroy has irrecoverable implications where directories and registries 
are permanently deleted. For some applications this could mean loosing valuable 
data. It might be a good idea to introduce a {{--force}} switch, so that 
admins/application-owners are given a chance to ensure they know what they are 
doing.

This is something in-line with *git clean*. When invoked by default it fails 
with a message saying {{-f}} is mandatory (unless the git config variable 
clean.requireForce is set to false). If the user is confident he/she will 
re-run the command with the force switch. 

Slider could do something similar.

  was:
Slider destroy has irrecoverable implications where directories and registries 
are permanently deleted. For some applications this could mean loosing valuable 
data. It might be a good idea to introduce a {{--force}} switch, so that 
admins/application-owners are given a chance to ensure they know what they are 
doing.

This is something in-line with "git clean". When invoked by default it fails 
with a message saying {{--force}} is mandatory (unless the git config variable 
clean.requireForce is set to false). If the user knows what he/she is doing 
they will re-run the command with {{--force}} switch. 

Slider could do something similar.


> Introduce --force switch for slider destroy command
> ---
>
> Key: SLIDER-657
> URL: https://issues.apache.org/jira/browse/SLIDER-657
> Project: Slider
>  Issue Type: Bug
>  Components: client
>Affects Versions: Slider 0.60
>Reporter: Gour Saha
>
> Slider destroy has irrecoverable implications where directories and 
> registries are permanently deleted. For some applications this could mean 
> loosing valuable data. It might be a good idea to introduce a {{--force}} 
> switch, so that admins/application-owners are given a chance to ensure they 
> know what they are doing.
> This is something in-line with *git clean*. When invoked by default it fails 
> with a message saying {{-f}} is mandatory (unless the git config variable 
> clean.requireForce is set to false). If the user is confident he/she will 
> re-run the command with the force switch. 
> Slider could do something similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLIDER-657) Introduce --force switch for slider destroy command

2014-11-18 Thread Gour Saha (JIRA) 
Gour Saha created SLIDER-657:


 Summary: Introduce --force switch for slider destroy command
 Key: SLIDER-657
 URL: https://issues.apache.org/jira/browse/SLIDER-657
 Project: Slider
  Issue Type: Bug
  Components: client
Affects Versions: Slider 0.60
Reporter: Gour Saha


Slider destroy has irrecoverable implications where directories and registries 
are permanently deleted. For some applications this could mean loosing valuable 
data. It might be a good idea to introduce a {{--force}} switch, so that 
admins/application-owners are given a chance to ensure they know what they are 
doing.

This is something in-line with "git clean". When invoked by default it fails 
with a message saying {{--force}} is mandatory (unless the git config variable 
clean.requireForce is set to false). If the user knows what he/she is doing 
they will re-run the command with {{--force}} switch. 

Slider could do something similar.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[VOTE] Release Apache Slider 0.60.0 incubating

2014-11-18 Thread Josh Elser 

Hi,

The Apache Slider project has voted to release 0.60.0-incubating. The 
team voted to release these artifacts with 6 +1's and nothing else. 2 of 
the 6 votes were from IPMC members.


Vote thread: http://s.apache.org/a6O
Result: http://s.apache.org/e3C

Staged artifacts: 
http://people.apache.org/~stevel/slider/slider-release-0.60.0-incubating-rc1 



SHA1: c2c06d3532708ac2ed765ebc465edda1b0067025
Source: 
https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;a=commit;h=c2c06d3532708ac2ed765ebc465edda1b0067025 


Git tag: "release-0.60.0-incubating-rc1"

PGP key: 
http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=ste...@apache.org


Basic build/test instructions: 
http://slider.incubator.apache.org/developing/building.html


Please vote on releasing the above as Apache Slider 0.60.0-incubating. 
This vote will be open for 72 hours.


Thanks!

- Apache Slider team

Re: how to get the quicklinks from the slider UI?

2014-11-18 Thread Sumit Mohanty 
Here it is for HBase

http://c6403.ambari.apache.org:8088/proxy/application_1415914904020_0021/
http://c6403.ambari.apache.org:8088/proxy/application_1415914904020_0021/ws/v1/slider/publisher/slider
http://c6403.ambari.apache.org:8088/proxy/application_1415914904020_0021/ws/v1/slider/publisher/slider/quicklinks
"org.apache.slider.monitor": "
http://c6403.ambari.apache.org:34525/master-status";
,

Its not quite the least amount of click :-)

QuickLinks is just a named export group and Slider App View picks it up and
shows in the App Page where it is indeed least amount of click.

In the next releases we should promote it to a top level link in the AM UI
as well.

On Tue, Nov 18, 2014 at 7:45 AM, Steve Loughran 
wrote:

> I know we publish some quicklink URLs, but do we have an easy way to get to
> them from the web UI itself?
>
> I'm doing a storm demo tomorrow and I'm trying to come up with the
> least-number-of-clicks strategy to show going from YARN UI to the links to
> the storm web UI page
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

how to get the quicklinks from the slider UI?

2014-11-18 Thread Steve Loughran 
I know we publish some quicklink URLs, but do we have an easy way to get to
them from the web UI itself?

I'm doing a storm demo tomorrow and I'm trying to come up with the
least-number-of-clicks strategy to show going from YARN UI to the links to
the storm web UI page

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

[jira] [Commented] (SLIDER-633) Slider should support invocation via Oozie

2014-11-18 Thread Jonathan Maron (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLIDER-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216233#comment-14216233
 ] 

Jonathan Maron commented on SLIDER-633:
---

Why are you setting the appConf setting in SliderClient:

String tokenCredentials = conf.get("mapreduce.job.credentials.binary");
if (tokenCredentials != null)
  appConf.set("mapreduce.job.credentials.binary", tokenCredentials);

It doesn't seem to be leveraged anywhere.

> Slider should support invocation via Oozie
> --
>
> Key: SLIDER-633
> URL: https://issues.apache.org/jira/browse/SLIDER-633
> Project: Slider
>  Issue Type: Improvement
>Affects Versions: Slider 0.50
>Reporter: Lee Yang
> Attachments: fix_oozie_launch.patch
>
>
> In a secure Hadoop installation, when attempting to launch a slider 
> application via an Oozie shell-action, I see the following exception:
> {noformat}
> Stdoutput org.apache.hadoop.ipc.RemoteException(java.io.IOException): 
> Delegation Token can be issued only with kerberos or web authentication
> Stdoutput at 
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getDelegationToken(FSNamesystem.java:6757)
> Stdoutput at 
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.getDelegationToken(NameNodeRpcServer.java:499)
> Stdoutput at 
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.getDelegationToken(ClientNamenodeProtocolServerSideTranslatorPB.java:921)
> Stdoutput at 
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
> Stdoutput at 
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:585)
> Stdoutput at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:928)
> Stdoutput at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2013)
> Stdoutput at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2009)
> Stdoutput at java.security.AccessController.doPrivileged(Native Method)
> Stdoutput at javax.security.auth.Subject.doAs(Subject.java:415)
> Stdoutput at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1637)
> Stdoutput at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2007)
> Stdoutput 
> Stdoutput at org.apache.hadoop.ipc.Client.call(Client.java:1411)
> Stdoutput at org.apache.hadoop.ipc.Client.call(Client.java:1364)
> Stdoutput at 
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:206)
> Stdoutput at com.sun.proxy.$Proxy17.getDelegationToken(Unknown Source)
> Stdoutput at 
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.getDelegationToken(ClientNamenodeProtocolTranslatorPB.java:864)
> Stdoutput at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> Stdoutput at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> Stdoutput at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Stdoutput at java.lang.reflect.Method.invoke(Method.java:601)
> Stdoutput at 
> org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:187)
> Stdoutput at 
> org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:102)
> Stdoutput at com.sun.proxy.$Proxy18.getDelegationToken(Unknown Source)
> Stdoutput at 
> org.apache.hadoop.hdfs.DFSClient.getDelegationToken(DFSClient.java:947)
> Stdoutput at 
> org.apache.hadoop.hdfs.DistributedFileSystem.getDelegationToken(DistributedFileSystem.java:1305)
> Stdoutput at 
> org.apache.hadoop.fs.FileSystem.collectDelegationTokens(FileSystem.java:527)
> Stdoutput at 
> org.apache.hadoop.fs.FileSystem.addDelegationTokens(FileSystem.java:505)
> Stdoutput at 
> org.apache.slider.core.launch.AppMasterLauncher.addSecurityTokens(AppMasterLauncher.java:209)
> Stdoutput at 
> org.apache.slider.core.launch.AppMasterLauncher.completeAppMasterLaunch(AppMasterLauncher.java:183)
> Stdoutput at 
> org.apache.slider.core.launch.AppMasterLauncher.submitApplication(AppMasterLauncher.java:214)
> Stdoutput at 
> org.apache.slider.client.SliderClient.launchApplication(SliderClient.java:1127)
> Stdoutput at 
> org.apache.slider.client.SliderClient.startCluster(SliderClient.java:771)
> Stdoutput at 
> org.apache.slider.client.SliderClient.actionCreate(SliderClient.java:515)
> Stdoutput at 
> org.apache.slider.client.SliderClient.runService(SliderClient.java:295)
> Stdoutput at 
> org.apache.slider.core.main.ServiceLauncher.launchService(ServiceLauncher.java:186)
> Stdoutput at 
> org.apache.slider.core.main.ServiceLauncher.launchServiceRobustly(Service

[jira] [Created] (SLIDER-656) drop providers/hbase and providers/accumulo

2014-11-18 Thread Steve Loughran (JIRA) 
Steve Loughran created SLIDER-656:
-

 Summary: drop providers/hbase and providers/accumulo
 Key: SLIDER-656
 URL: https://issues.apache.org/jira/browse/SLIDER-656
 Project: Slider
  Issue Type: Improvement
  Components: build
Affects Versions: Slider 0.60
Reporter: Steve Loughran
Assignee: Steve Loughran


the hbase and accumulo provicer modules are not part of the release, but have 
been retained in build and purely for testing, specifically some of the flexing 
and failures. The funtests test suites do more than the older tests.

We can drop these modules now for faster builds and less confusion and 
maintenance costs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLIDER-655) split app packages out of slider POM for independent releases

2014-11-18 Thread Steve Loughran (JIRA) 
Steve Loughran created SLIDER-655:
-

 Summary: split app packages out of slider POM for independent 
releases
 Key: SLIDER-655
 URL: https://issues.apache.org/jira/browse/SLIDER-655
 Project: Slider
  Issue Type: Improvement
  Components: app-package
Affects Versions: Slider 0.60
Reporter: Steve Loughran


the app-packages/* projects are set up as sub-projects of slider, yet they have 
their own independent versions set by maven properties. This broken the release 
process, and will complicate releasing app packages independently.

proposed:

make each app package an independent build, depending on slider components, but 
in their own builds



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[VOTE RESULTS] Slider 0.60

2014-11-18 Thread Steve Loughran 
We've reached the end of the vote, here are the results:

+1 : 6
 0 : 0
-1 : 0

accordingly, the vote has gone through ... which means that we can proceed
to the next stage: seeking approval on the incubator general list

thank you to all who tested and voted!

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.