[jira] [Created] (SLIDER-256) Use package information form metainfo.xml

Sumit Mohanty created SLIDER-256: Summary: Use package information form metainfo.xml Key: SLIDER-256 URL: https://issues.apache.org/jira/browse/SLIDER-256 Project: Slider Issue Type: Bug

Re: Start a role always IN_PROGRESS status

Thanks! It works. I should look at your sample more carefully. My start implementation is a little bit complex. I will first bootstrap the catalog. Vertica uses spread to communicate with each other. So I also need to update the configuration file of spread to include all the hostnames Vertica

Re: Start a role always IN_PROGRESS status

If you are using the helpers provided in the resource management library then you can set the wait_for_finish to False. Execute(process_cmd, user=params.app_user, logoutput=False, *wait_for_finish=False* ) See the memecached sample I shared. How does your start() impl

Re: Start a role always IN_PROGRESS status

Actually Vertica is not killed by the script and run perfectly. But Slider will think that Vertica is killed and try again. On 07/24/2014 04:52 PM, Rui Zhang wrote: Hi, thanks for your reply. I know why it hangs. I have read the code of agent/PythonExecutor.py It blocks in the line "process.

Re: Start a role always IN_PROGRESS status

Hi, thanks for your reply. I know why it hangs. I have read the code of agent/PythonExecutor.py It blocks in the line "process.communicate()". My start command will spawn three child processes. Maybe this line is waiting for the three to finish? I am not very familiar with how the communicat

Re: Start a role always IN_PROGRESS status

My guess is that start() does not complete or fails and gets retried few times and then eventually fails. Can you share the agent logs? We have a new release now 0.40 - can you port your package over to 0.40? If you can share your package I can help you do that. In any case, only critical change i

Start a role always IN_PROGRESS status

Hi, I can start my own created package now. But it always stay IN_PROGRESS status according to the log and after a long time it shows Failed. However, my application runs perfectly without any errors. Why is this? How to determine the start is completed or not? Thanks. -- Rui Zhang Software

Re: Bringing up HBase cluster with Slider

On Jul 24, 2014, at 1:47 PM, Nitin Aggarwal wrote: > Hi, > > I was trying to bring hbase cluster with Slider. As we have non-yarn HBase > installation also on the machines, I faced issue due to HBASE_HOME variable > not set correctly. > > I resolved it by setting it explicitly in > "app-packa

Bringing up HBase cluster with Slider

Hi, I was trying to bring hbase cluster with Slider. As we have non-yarn HBase installation also on the machines, I faced issue due to HBASE_HOME variable not set correctly. I resolved it by setting it explicitly in "app-packages/hbase/package/templates/hbase-env.sh.j2" as export HBASE_HOME={{hba

Re: password handling

To be clear, ["root", "instance.secret"] is a list of usernames / keys by which to store and retrieve password / secret info. Accumulo's instance.secret is the name of another shared secret it needs. The default implementation of CredentialProvider stores the credentials by key in a no-password J

Re: password handling

On Jul 23, 2014, at 4:03 PM, Billie Rinaldi wrote: > Accumulo requires a couple of sensitive pieces of information to be > provided when it is starting up (including the Accumulo root user's > password). Those are currently provided in the appConfig.json file. > Hadoop common is adding a Creden