[jira] [Created] (SLIDER-851) Support instance level configuration
Siyuan Hua created SLIDER-851: - Summary: Support instance level configuration Key: SLIDER-851 URL: https://issues.apache.org/jira/browse/SLIDER-851 Project: Slider Issue Type: New Feature Reporter: Siyuan Hua Use case, in kafka, component broker would have multiple instances running with some different configuration (for example, unique brokerid) There is no need to define different components for just different configurations -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLIDER-648) Support component level properties
[
https://issues.apache.org/jira/browse/SLIDER-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14267948#comment-14267948
]
Siyuan Hua commented on SLIDER-648:
---
It's just not so intuitive. When I first look at the configuration. I think the
key,value under components would be picked up and override what's been set in
global. If it's not picked, why do we even need that components section? We can
put everything in that site.COMPONENT tree, right?
Other thing I noticed is that you can also define them in separate file
(configuration/COMPONENT0.xml). These ways of configuration really make me feel
confusing.
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] [Commented] (SLIDER-665) Allow extensibility of the Slider AM Web UI to provide application specific end points
[ https://issues.apache.org/jira/browse/SLIDER-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14225014#comment-14225014 ] Siyuan Hua commented on SLIDER-665: --- Maybe I was wrong, but instead of using YARN proxy, why not having standalone but central web service server running on slider AM and register as service. Client can find the node which hosts the server and connect to it directly. Allow extensibility of the Slider AM Web UI to provide application specific end points -- Key: SLIDER-665 URL: https://issues.apache.org/jira/browse/SLIDER-665 Project: Slider Issue Type: Task Components: appmaster, Web REST Affects Versions: Slider 0.60 Reporter: Sumit Mohanty Priority: Critical Slider AppMaster UI provides a REST end point for various metadata related to the application and general purpose application status. Applications can also explicitly export config and URLs (any data for that matter) and that is also available through the REST end point. What is not possible is for the application to report back custom data sets at regular intervals and have it available through the AM REST endpoint. The advantage of such a support would be for applications that do not need a comprehensive web service and can extend the AppMaster REST endpoint to provide application specific data. _Its worth investigating if the REST API should be readonly or it is also expected to have support for PUT and POST._ Such feature will mean: * Allow agents to send custom stats to the AM (arbitrary JSON structure) * Make per component instance JSON stats available through the Slider AM Web Service -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLIDER-648) Support component level properties
Siyuan Hua created SLIDER-648:
-
Summary: 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] [Commented] (SLIDER-337) Agent error when trying to deploy Accumulo
[
https://issues.apache.org/jira/browse/SLIDER-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14190918#comment-14190918
]
Siyuan Hua commented on SLIDER-337:
---
I may be wrong, but the right solution should be configurable. I'm using
linuxmint. It should belongs to AptProvider. So user should be able to set the
provider if the system cannot recognize
Agent error when trying to deploy Accumulo
---
Key: SLIDER-337
URL: https://issues.apache.org/jira/browse/SLIDER-337
Project: Slider
Issue Type: Bug
Components: agent-provider
Environment: Gentoo Linux, develop branch (035ebbd),
Hadoop-2.6.0-SNAPSHOT (r1619002)
Reporter: Josh Elser
Assignee: Josh Elser
Fix For: Slider 0.60
Tried to start an Accumulo cluster:
{noformat}
slider create accumulo --image
hdfs://localhost:8020/slider/agent/slider-agent.tar.gz --template
/home/elserj/slider/app-packages/accumulo/target/apache-slider-accumulo-1.6.0-app-package-0.40/appConfig.json
--resources
/home/elserj/slider/app-packages/accumulo/target/apache-slider-accumulo-1.6.0-app-package-0.40/resources.json
{noformat}
SliderAM came up, but no Accumulo procs got started. Looking at the AM
webapp, the Accumulo master container kept cycling. Dug around in the
NM/container logs dir, and found the following stack:
{noformat}
Traceback (most recent call last):
File
.../nm-local-dir/usercache/elserj/appcache/application_1408503547578_0002/container_1408503547578_0002_01_21/app/definition/package/scripts/accumulo_master.py,
line 24, in module
AccumuloScript('master').execute()
File
.../nm-local-dir/usercache/elserj/appcache/application_1408503547578_0002/container_1408503547578_0002_01_21/infra/agent/slider-agent/resource_management/libraries/script/script.py,
line 114, in execute
method(env)
File
.../nm-local-dir/usercache/elserj/appcache/application_1408503547578_0002/filecache/19/apache-slider-accumulo-1.6.0-app-package-0.40.zip/package/scripts/accumulo_script.py,
line 82, in start
self.configure(env) # for security
File
.../nm-local-dir/usercache/elserj/appcache/application_1408503547578_0002/filecache/19/apache-slider-accumulo-1.6.0-app-package-0.40.zip/package/scripts/accumulo_script.py,
line 76, in configure
setup_conf_dir(name=self.component)
File
.../tmp/nm-local-dir/usercache/elserj/appcache/application_1408503547578_0002/filecache/19/apache-slider-accumulo-1.6.0-app-package-0.40.zip/package/scripts/accumulo_configuration.py,
line 31, in setup_conf_dir
recursive = True
File
.../nm-local-dir/usercache/elserj/appcache/application_1408503547578_0002/container_1408503547578_0002_01_21/infra/agent/slider-agent/resource_management/core/base.py,
line 148, in __init__
self.env.run()
File
.../nm-local-dir/usercache/elserj/appcache/application_1408503547578_0002/container_1408503547578_0002_01_21/infra/agent/slider-agent/resource_management/core/environment.py,
line 149, in run
self.run_action(resource, action)
File
.../nm-local-dir/usercache/elserj/appcache/application_1408503547578_0002/container_1408503547578_0002_01_21/infra/agent/slider-agent/resource_management/core/environment.py,
line 109, in run_action
resource.provider)
File
.../nm-local-dir/usercache/elserj/appcache/application_1408503547578_0002/container_1408503547578_0002_01_21/infra/agent/slider-agent/resource_management/core/providers/__init__.py,
line 72, in find_provider
if resource in provider[env.system.os_family]:
KeyError: 'gentoo base system'
{noformat}
I'm rusty on my Python, but I believe this means that in
{{slider-agent/src/main/python/resource_management/core/providers/__init__.py}}
{noformat}
if resource in provider[env.system.os_family]:
{noformat}
should be
{noformat}
if env.system.os_family in provider:
if resource in provider[env.system.os_family]:
{noformat}
to avoid the Exception when the key doesn't exist (alternatively try/except,
too), and get down to the {{default}} case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SLIDER-590) Need some convinient debug ability of command script during/post development time
Siyuan Hua created SLIDER-590: - Summary: Need some convinient debug ability of command script during/post development time Key: SLIDER-590 URL: https://issues.apache.org/jira/browse/SLIDER-590 Project: Slider Issue Type: Bug Reporter: Siyuan Hua Nowadays, whatever errors I made in command script to launch the component, I have to modify the python code repackage and redeployed to hdfs and relaunch the application. It's quite inconvenient. I hope there is a way to run, test and debug the command script right after they are installed on target machine. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
