Steve Loughran created SLIDER-650:
-
Summary: regression: local zk nodes not being deleted on instance
destroy
Key: SLIDER-650
URL: https://issues.apache.org/jira/browse/SLIDER-650
Project: Slider
[
https://issues.apache.org/jira/browse/SLIDER-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved SLIDER-650.
---
Resolution: Fixed
regression: local zk nodes not being deleted on instance destroy
Steve Loughran created SLIDER-651:
-
Summary: intermittent failure of TestStandaloneAgentAM on windows
Key: SLIDER-651
URL: https://issues.apache.org/jira/browse/SLIDER-651
Project: Slider
Hi
The updated RC1 release of slider is up for review and vote. Please
download and review it
all changes in this release are listed at:
https://issues.apache.org/jira/browse/SLIDER/fixforversion/12327198/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-summary-panel
Main changes
There's some discussion in general@incubator that a git commit must be
supplied for a release, not a branch or (movable) tag.
the commit used for this release is: c2c06d3
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is
[
https://issues.apache.org/jira/browse/SLIDER-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14212714#comment-14212714
]
ASF subversion and git services commented on SLIDER-544:
Commit
Everytime I change appConfig.json and resources.json. Do I have to
repackage the zip file and redeploy the file to hdfs?
Thanks!
No, those files are only needed as inputs to create command.
The ZIP package is expected to have default versions of the file as a
reference - it does not need them for operation.
In the current develop or releases/slider-60 we have modified the names
to have the word default.
On Fri, Nov 14,
Perhaps I’m misunderstanding your question, but in general, if making
modifications to those files, you can simply create a new application instance
referencing the new versions of the file from the command line:
./slider create app name —template appConfig path —resources resources
file path
So actually you don't need appConfig.json and resources.json in the ZIP
package?
On Fri, Nov 14, 2014 at 12:05 PM, Jon Maron jma...@hortonworks.com wrote:
Perhaps I’m misunderstanding your question, but in general, if making
modifications to those files, you can simply create a new application
Nope. This is what I do typically.
* Get an application package zip file
* Extract the appConfig-default.json and resources-default.json from the
package
* Rename the files to appConfig.json and resources.json respectively and
edit as needed
* Use install-package to upload the application
+1.
Modify the following to rc1,
source at
https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;a=shortlog;h=refs/tags/release-0.60.0-incubating-rc0
Verified SHA and MD5 for both the tar ball and the zip file.
The pgp signatures also verify against the public key.
Created a clean
I'm getting confused. After you edit your appConfig.json and
resources.json. You don't put it back in your package zip file? So the
appConfig-default.json and resource-default.json is outdated?
Another question is actually I'm asking how to change the configuration
without recreate the cluster.
How to change log level for Slider AM?
Thanks!
I'm getting confused. After you edit your appConfig.json and resources.json.
You don't put it back in your package zip file? So the appConfig-default.json
and resource-default.json is outdated?
The file in the .zip package is not used by the running application. The
files that are used are the
I'm actually using 0.40
On Fri, Nov 14, 2014 at 4:21 PM, Sumit Mohanty smoha...@hortonworks.com
wrote:
I'm getting confused. After you edit your appConfig.json and
resources.json.
You don't put it back in your package zip file? So the
appConfig-default.json
and resource-default.json is
Hi all,
In the document, I got that slider will try to recover on container
failure. But in my test application it doesn't
I'm using the 0.40 release. build from source
Here is what I get.
*If I kill the child process *
The agent check_process_status method will raise ComponentIsNotRunning and
Is it possible for you to pick up the latest RC (0.60)? I can help you
update the existing application package, if needed.
Meanwhile, for 0.40, the log4j.properties file in
slider-client-install-dir/conf can be modified to up the log level and the
create call will push the file as a localized
The only problem is I have to upgrade to hadoop 2.6?
On Fri, Nov 14, 2014 at 5:08 PM, Sumit Mohanty smoha...@hortonworks.com
wrote:
Is it possible for you to pick up the latest RC (0.60)? I can help you
update the existing application package, if needed.
Meanwhile, for 0.40, the
This is not possible when the app is running. Yarn does have a support
for
that. You need to stop the application and then modify the values. After
topping the application you need to edit the resources.json file in HDFS
to modify the value
(e.g.
*If I kill the child process *
So are you observing that a replacement container instance is never
started? Can you check the AM log? What is expected to happen here is as
follows:
- process goes down, and then agent goes down, AM notices, asks for a new
container from Yarn.
if you want the agent
On Fri, Nov 14, 2014 at 5:14 PM, hsy...@gmail.com hsy...@gmail.com wrote:
This is not possible when the app is running. Yarn does have a support
for
that. You need to stop the application and then modify the values. After
topping the application you need to edit the resources.json file in
Under conf directory there is a file named *log4j-server.properties*. Just
edit that file and change *log4j.rootLogger* from INFO to what you like.
Then do slider stop and slider start. The new level for Slider AM will take
effect. The *slider.log* file is rotated as well on a 100KB size
23 matches
Mail list logo
