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 machine and HADOOP_HOME is set in bashrc,
but you don't want to use hadoop for some reason. In that case Hbase will
face connection issues as it'll try to contact the Hadoop host(as
HADOOP_HOME is present in bashrc) which is not running because it is
standalone setup. On the other hand if you are running Hbase in pseudo
distributed mode and if you haven't set HADOOP_HOME in bashrc, it would
I'm sorry to be a pest of questions. I am actually not able to understand
this. Pardon my ignorance.
On Sun, May 12, 2013 at 1:14 AM, Amandeep Khurana <[EMAIL PROTECTED]> wrote:
> 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 <[EMAIL PROTECTED]> wrote:
> > 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
> > if I have a standalone setup on my local FS.
> > Thank you so much for your time.
> > Warm Regards,
> > Tariq
> > cloudfront.blogspot.com