[jira] [Commented] (SLIDER-298) Add an application package template

[ https://issues.apache.org/jira/browse/SLIDER-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14088862#comment-14088862 ] ASF subversion and git services commented on SLIDER-298: Commit 37

[jira] [Commented] (SLIDER-290) Slider upgrade

[ https://issues.apache.org/jira/browse/SLIDER-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14088587#comment-14088587 ] Sumit Mohanty commented on SLIDER-290: -- Scenario: User is using an older version of S

[jira] [Created] (SLIDER-299) What is the recommendation if a user wants a single active version of Slider

Sumit Mohanty created SLIDER-299: Summary: What is the recommendation if a user wants a single active version of Slider Key: SLIDER-299 URL: https://issues.apache.org/jira/browse/SLIDER-299 Project: S

[jira] [Updated] (SLIDER-167) Automatically copy slider-agent.tar.gz when creating an application

[ https://issues.apache.org/jira/browse/SLIDER-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated SLIDER-167: - Component/s: (was: appmaster) client > Automatically copy slider-agent.tar.g

SLIDER-167: Automatically copy slider-agent.tar.gz when creating an application

While I was listing the upgrade scenarios, it seems that the solution for SLIDER-167 will have to be discussed in light of upgrade. If each application instance has their own copy of AppMaster jars (today they do) and the Agent tarball then user can selectively upgrade Slider on a per app-instance

Slider-develop - Build # 139 - Failure

The Apache Jenkins build system has built Slider-develop (build #139) Status: Failure Check console output at https://builds.apache.org/job/Slider-develop/139/ to view the results.

Slider-develop - Build # 138 - Aborted

The Apache Jenkins build system has built Slider-develop (build #138) Status: Aborted Check console output at https://builds.apache.org/job/Slider-develop/138/ to view the results.

[jira] [Commented] (SLIDER-239) Component instances should be able to advertise associated ports

[ https://issues.apache.org/jira/browse/SLIDER-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14088296#comment-14088296 ] Sumit Mohanty commented on SLIDER-239: -- Look at the memcached sample in "develop" bra

[jira] [Commented] (SLIDER-239) Component instances should be able to advertise associated ports

[ https://issues.apache.org/jira/browse/SLIDER-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14088279#comment-14088279 ] Rui Zhang commented on SLIDER-239: -- Thanks. But how to get the port number in the python

[jira] [Commented] (SLIDER-239) Component instances should be able to advertise associated ports

[ https://issues.apache.org/jira/browse/SLIDER-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14088256#comment-14088256 ] Jonathan Maron commented on SLIDER-239: --- Just a thought: there already is the conve

[jira] [Resolved] (SLIDER-273) Add ability to specify a port as shared across component instances or not

[ https://issues.apache.org/jira/browse/SLIDER-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved SLIDER-273. -- Resolution: Fixed Adding {DO_NOT_PROPAGATE} to the port allocation directive in the app config

[jira] [Resolved] (SLIDER-298) Add an application package template

[ https://issues.apache.org/jira/browse/SLIDER-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved SLIDER-298. -- Resolution: Fixed A template is added to the repo. Need to explore mvn support to create templ

[jira] [Resolved] (SLIDER-294) Clean up memcached app packages for Windows and Linux

[ https://issues.apache.org/jira/browse/SLIDER-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved SLIDER-294. -- Resolution: Fixed > Clean up memcached app packages for Windows and Linux > ---

[jira] [Resolved] (SLIDER-293) On Windows slider agent should be able to execute commands and not wait for completion

[ https://issues.apache.org/jira/browse/SLIDER-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved SLIDER-293. -- Resolution: Fixed > On Windows slider agent should be able to execute commands and not wait for

[jira] [Resolved] (SLIDER-219) A service may ask for more than one dynamically allocated port as part of the same configuration

[ https://issues.apache.org/jira/browse/SLIDER-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved SLIDER-219. -- Resolution: Fixed > A service may ask for more than one dynamically allocated port as part of t

[jira] [Commented] (SLIDER-298) Add an application package template

[ https://issues.apache.org/jira/browse/SLIDER-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14088237#comment-14088237 ] ASF subversion and git services commented on SLIDER-298: Commit 60

[jira] [Resolved] (SLIDER-239) Component instances should be able to advertise associated ports

[ https://issues.apache.org/jira/browse/SLIDER-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved SLIDER-239. -- Resolution: Fixed A component can specify the following in metainfo.xml to advertise its ports:

[jira] [Created] (SLIDER-298) Add an application package template

Sumit Mohanty created SLIDER-298: Summary: Add an application package template Key: SLIDER-298 URL: https://issues.apache.org/jira/browse/SLIDER-298 Project: Slider Issue Type: Bug

[jira] [Updated] (SLIDER-298) Add an application package template

[ https://issues.apache.org/jira/browse/SLIDER-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated SLIDER-298: - Sprint: Slider August #1 > Add an application package template >

[jira] [Resolved] (SLIDER-272) Application should specify the config types to publish

[ https://issues.apache.org/jira/browse/SLIDER-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved SLIDER-272. -- Resolution: Fixed can be used to specify which configs to publish. To publish all leave it un

[jira] [Resolved] (SLIDER-271) When a container is releases the AppMaster should not monitor heartbeats from that container

[ https://issues.apache.org/jira/browse/SLIDER-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved SLIDER-271. -- Resolution: Fixed > When a container is releases the AppMaster should not monitor heartbeats fr

[jira] [Commented] (SLIDER-296) AM to notify containers on managed container release

[ https://issues.apache.org/jira/browse/SLIDER-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087995#comment-14087995 ] ASF subversion and git services commented on SLIDER-296: Commit 06

[jira] [Commented] (SLIDER-296) AM to notify containers on managed container release

[ https://issues.apache.org/jira/browse/SLIDER-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087997#comment-14087997 ] ASF subversion and git services commented on SLIDER-296: Commit d1

[jira] [Commented] (SLIDER-296) AM to notify containers on managed container release

[ https://issues.apache.org/jira/browse/SLIDER-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087994#comment-14087994 ] ASF subversion and git services commented on SLIDER-296: Commit 3b

[jira] [Resolved] (SLIDER-270) Calling flex (down) the second time does not work

[ https://issues.apache.org/jira/browse/SLIDER-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved SLIDER-270. --- Resolution: Fixed > Calling flex (down) the second time does not work > -

[jira] [Created] (SLIDER-297) TestAppStateContainerFailure#testShortLivedFail fails due to startFailed being 0

Ted Yu created SLIDER-297: - Summary: TestAppStateContainerFailure#testShortLivedFail fails due to startFailed being 0 Key: SLIDER-297 URL: https://issues.apache.org/jira/browse/SLIDER-297 Project: Slider

Slider-develop - Build # 137 - Still Failing

The Apache Jenkins build system has built Slider-develop (build #137) Status: Still Failing Check console output at https://builds.apache.org/job/Slider-develop/137/ to view the results.

[jira] [Commented] (SLIDER-295) Unit test failure caused by wrong parameter type in AppState#onCompletedNode()

[ https://issues.apache.org/jira/browse/SLIDER-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087786#comment-14087786 ] ASF subversion and git services commented on SLIDER-295: Commit 53

[jira] [Updated] (SLIDER-295) Unit test failure caused by wrong parameter type in AppState#onCompletedNode()

[ https://issues.apache.org/jira/browse/SLIDER-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated SLIDER-295: -- Summary: Unit test failure caused by wrong parameter type in AppState#onCompletedNode() (was: Unit test failur

[jira] [Resolved] (SLIDER-295) Unit test failure caused by wrong parameter type in AppState#onCompletedNode()

[ https://issues.apache.org/jira/browse/SLIDER-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu resolved SLIDER-295. --- Resolution: Fixed > Unit test failure caused by wrong parameter type in AppState#onCompletedNode() >

[jira] [Assigned] (SLIDER-295) Unit test failure

[ https://issues.apache.org/jira/browse/SLIDER-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu reassigned SLIDER-295: - Assignee: Ted Yu > Unit test failure > - > > Key: SLIDER-295 >

[jira] [Commented] (SLIDER-295) Unit test failure

[ https://issues.apache.org/jira/browse/SLIDER-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087784#comment-14087784 ] Ted Yu commented on SLIDER-295: --- Calling roleInstance.getContainerId().toString() solves the

Slider-develop - Build # 136 - Still Failing

The Apache Jenkins build system has built Slider-develop (build #136) Status: Still Failing Check console output at https://builds.apache.org/job/Slider-develop/136/ to view the results.

Re: SLIDER-296 AM to notify containers on managed container release

On Wed, Aug 6, 2014 at 7:01 AM, Steve Loughran wrote: > https://issues.apache.org/jira/browse/SLIDER-296 > > I've just filed a new JIRA, SLIDER-296, on having the AM work with the > provider for managed releases of containers. > > 1. the AM could actually ask the provider to select nodes for rele

Re: SLIDER-296 AM to notify containers on managed container release

On Aug 6, 2014, at 10:01 AM, Steve Loughran wrote: > https://issues.apache.org/jira/browse/SLIDER-296 > > I've just filed a new JIRA, SLIDER-296, on having the AM work with the > provider for managed releases of containers. > > 1. the AM could actually ask the provider to select nodes for rele

SLIDER-296 AM to notify containers on managed container release

https://issues.apache.org/jira/browse/SLIDER-296 I've just filed a new JIRA, SLIDER-296, on having the AM work with the provider for managed releases of containers. 1. the AM could actually ask the provider to select nodes for releasing. Currently it picks nodes that are on machines with >1 insta

[jira] [Created] (SLIDER-296) AM to notify containers on managed container release

Steve Loughran created SLIDER-296: - Summary: AM to notify containers on managed container release Key: SLIDER-296 URL: https://issues.apache.org/jira/browse/SLIDER-296 Project: Slider Issue T

[jira] [Commented] (SLIDER-69) Uber JIRA: Slider apps to withstand failures

[ https://issues.apache.org/jira/browse/SLIDER-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087683#comment-14087683 ] Steve Loughran commented on SLIDER-69: -- AM to notify provider on planned node shutdown

[jira] [Resolved] (SLIDER-159) Jenkins testEcho failing

[ https://issues.apache.org/jira/browse/SLIDER-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved SLIDER-159. --- Resolution: Fixed appears fixed now > Jenkins testEcho failing > >

[jira] [Commented] (SLIDER-276) AgentProvider releases nodes that the AM has already been released after detecting heartbeat failure

[ https://issues.apache.org/jira/browse/SLIDER-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087678#comment-14087678 ] ASF subversion and git services commented on SLIDER-276: Commit 32

[jira] [Commented] (SLIDER-276) AgentProvider releases nodes that the AM has already been released after detecting heartbeat failure

[ https://issues.apache.org/jira/browse/SLIDER-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087673#comment-14087673 ] Steve Loughran commented on SLIDER-276: --- Issue here is that the agent heartbeat has

[jira] [Commented] (SLIDER-276) AgentProvider releases nodes that the AM has already been released after detecting heartbeat failure

[ https://issues.apache.org/jira/browse/SLIDER-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087674#comment-14087674 ] Steve Loughran commented on SLIDER-276: --- Fixed by having containerID passed from hea

[jira] [Resolved] (SLIDER-276) AgentProvider releases nodes that the AM has already been released after detecting heartbeat failure

[ https://issues.apache.org/jira/browse/SLIDER-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved SLIDER-276. --- Resolution: Fixed Fix Version/s: Slider 0.50 Assignee: Steve Loughran (was: T

[jira] [Created] (SLIDER-295) Unit test failure

Sumit Mohanty created SLIDER-295: Summary: Unit test failure Key: SLIDER-295 URL: https://issues.apache.org/jira/browse/SLIDER-295 Project: Slider Issue Type: Bug Components: test

[jira] [Commented] (SLIDER-284) Build and test against Hadoop 2.5 RC and release

[ https://issues.apache.org/jira/browse/SLIDER-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087541#comment-14087541 ] ASF subversion and git services commented on SLIDER-284: Commit ef

[jira] [Commented] (SLIDER-270) Calling flex (down) the second time does not work

[ https://issues.apache.org/jira/browse/SLIDER-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087540#comment-14087540 ] ASF subversion and git services commented on SLIDER-270: Commit d6

[jira] [Commented] (SLIDER-270) Calling flex (down) the second time does not work

[ https://issues.apache.org/jira/browse/SLIDER-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087529#comment-14087529 ] ASF subversion and git services commented on SLIDER-270: Commit 8d

[jira] [Commented] (SLIDER-294) Clean up memcached app packages for Windows and Linux

[ https://issues.apache.org/jira/browse/SLIDER-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087528#comment-14087528 ] ASF subversion and git services commented on SLIDER-294: Commit 40

[jira] [Commented] (SLIDER-293) On Windows slider agent should be able to execute commands and not wait for completion

[ https://issues.apache.org/jira/browse/SLIDER-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087526#comment-14087526 ] ASF subversion and git services commented on SLIDER-293: Commit 40

[jira] [Commented] (SLIDER-271) When a container is releases the AppMaster should not monitor heartbeats from that container

[ https://issues.apache.org/jira/browse/SLIDER-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087522#comment-14087522 ] ASF subversion and git services commented on SLIDER-271: Commit 40

[jira] [Commented] (SLIDER-272) Application should specify the config types to publish

[ https://issues.apache.org/jira/browse/SLIDER-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087520#comment-14087520 ] ASF subversion and git services commented on SLIDER-272: Commit 64

[jira] [Updated] (SLIDER-276) AgentProvider releases nodes that the AM has already been released after detecting heartbeat failure

[ https://issues.apache.org/jira/browse/SLIDER-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated SLIDER-276: -- Summary: AgentProvider releases nodes that the AM has already been released after detecting hea

Slider-develop - Build # 135 - Failure

The Apache Jenkins build system has built Slider-develop (build #135) Status: Failure Check console output at https://builds.apache.org/job/Slider-develop/135/ to view the results.

[jira] [Commented] (SLIDER-270) Calling flex (down) the second time does not work

[ https://issues.apache.org/jira/browse/SLIDER-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087426#comment-14087426 ] ASF subversion and git services commented on SLIDER-270: Commit d6

[jira] [Commented] (SLIDER-270) Calling flex (down) the second time does not work

[ https://issues.apache.org/jira/browse/SLIDER-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087421#comment-14087421 ] ASF subversion and git services commented on SLIDER-270: Commit df

[jira] [Commented] (SLIDER-270) Calling flex (down) the second time does not work

[ https://issues.apache.org/jira/browse/SLIDER-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087425#comment-14087425 ] ASF subversion and git services commented on SLIDER-270: Commit 8d

[jira] [Commented] (SLIDER-284) Build and test against Hadoop 2.5 RC and release

[ https://issues.apache.org/jira/browse/SLIDER-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087416#comment-14087416 ] ASF subversion and git services commented on SLIDER-284: Commit 04

[jira] [Commented] (SLIDER-270) Calling flex (down) the second time does not work

[ https://issues.apache.org/jira/browse/SLIDER-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087419#comment-14087419 ] ASF subversion and git services commented on SLIDER-270: Commit 29