Hello list,
Does Hbase read the environment variables set in
*~/.bashrc*file everytime I issue
*bin/start-hbase.sh*??What could be the possible reasons for that?Specially
if I have a standalone setup on my local FS.
Thank you so much for your time.
Warm Regards,
Tariq
The start script is a shell script and it forks a new shell when the
script is executed. That'll source the bashrc file.
On May 11, 2013, at 12:39 PM, Mohammad Tariq donta...@gmail.com wrote:
Hello list,
Does Hbase read the environment variables set in
*~/.bashrc*file everytime I
Hello Aman,
Thank you so much for the quick response. But why would that happen? I
mean the required env variables are present in hbase-env.sh already. What
is the need to source bashrc?
Consider a scenario wherein you want to run Hbase in standalone mode. You
have a Hadoop setup on the same
On Sat, May 11, 2013 at 1:02 PM, Mohammad Tariq donta...@gmail.com wrote:
Hello Aman,
Thank you so much for the quick response. But why would that happen? I
mean the required env variables are present in hbase-env.sh already. What
is the need to source bashrc?
Consider a scenario
Hello sir,
Long time :)
Yeah, my understanding was same as whatever you have written. But today I
noticed that Hbase is picking HADOOP_HOME from bashrc when I was trying to
run it in standalone mode(on my local FS). Although all the Hadoop daemons
were stopped and Hbase was configured to
The #!/usr/bin/bash command in the script tells the shell to execute the
script as a bash script. The execution is done by forking off a new shell
instance, inside of which the bashrc is sourced automatically. It's not a
HBase script specific phenomena.
Like you said - removing the HADOOP_HOME
I see. It was actually a Linux thing. Thank you so much for the
clarification.
Warm Regards,
Tariq
cloudfront.blogspot.com
On Sun, May 12, 2013 at 4:51 AM, Amandeep Khurana ama...@gmail.com wrote:
The #!/usr/bin/bash command in the script tells the shell to execute the
script as a bash
