You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@flume.apache.org by Lior Harel <ha...@gmail.com> on 2011/08/17 14:50:42 UTC

set daemon physical name

I have setup the collector to run on the same machine as the master. When
running the collector as a daemon I couldn't find a way to specify its
physical name and it always registers as localhost. So I'm not sure how to
configure the agents' collectorSource, localhost?

is there a way to specify a physical name for the daemon's node?

also, I know this configuration (master + collector on the same machine) is
considered pseudo distributed mode (for dev purposes mainly), assuming we
roll out incrementally with limited number of events at the beginning, is
this configuration reasonable?


Thanks.

Re: set daemon physical name

Posted by Lior Harel <ha...@gmail.com>.
you were right, the hostname command return the machine name. but the
/etc/hosts file had some wrong configuration. thanks for the assistance.


On Wed, Aug 17, 2011 at 7:58 PM, Mike <mi...@gmail.com> wrote:

> Might be a reverse DNS issue - is the host's proper name in the /etc/hosts
> file?
>
> On Wed, Aug 17, 2011 at 12:18 PM, Lior Harel <ha...@gmail.com> wrote:
> > Thanks for the quick response, so I guess I'm having an issue here as the
> > node registers as localhost. (issuing hostname command yields the machine
> > name not localhost)
> > do you have any idea? could it be related to same machine as the master
> > configuration?
> >
> > On Wed, Aug 17, 2011 at 6:59 PM, NerdyNick <ne...@gmail.com> wrote:
> >>
> >> So flume masters, collectors, and agent nodes should be registering
> >> there physical name as whatever there hostname is, as returned by the
> >> hostname command. That being said you can also create a logical node
> >> and map it that way. You can also use physical DNS/IP's for the Agent
> >> Sinks and Collector Source's. I currently do it this way as it allows
> >> me to use multi master better, but does bring a slight layer of
> >> confusion.
> >>
> >> As for the configuration, I don't see a massive problem with it as
> >> long as you aren't planning to pump a very large amount of traffic at
> >> it.
> >>
> >> On Wed, Aug 17, 2011 at 6:50 AM, Lior Harel <ha...@gmail.com>
> wrote:
> >> > I have setup the collector to run on the same machine as the master.
> >> > When
> >> > running the collector as a daemon I couldn't find a way to specify its
> >> > physical name and it always registers as localhost. So I'm not sure
> how
> >> > to
> >> > configure the agents' collectorSource, localhost?
> >> > is there a way to specify a physical name for the daemon's node?
> >> > also, I know this configuration (master + collector on the same
> machine)
> >> > is
> >> > considered pseudo distributed mode (for dev purposes mainly), assuming
> >> > we
> >> > roll out incrementally with limited number of events at the beginning,
> >> > is
> >> > this configuration reasonable?
> >> >
> >> > Thanks.
> >>
> >>
> >>
> >> --
> >> Nick Verbeck - NerdyNick
> >> ----------------------------------------------------
> >> NerdyNick.com
> >> Coloco.ubuntu-rocks.org
> >
> >
>

Re: set daemon physical name

Posted by Mike <mi...@gmail.com>.
Might be a reverse DNS issue - is the host's proper name in the /etc/hosts file?

On Wed, Aug 17, 2011 at 12:18 PM, Lior Harel <ha...@gmail.com> wrote:
> Thanks for the quick response, so I guess I'm having an issue here as the
> node registers as localhost. (issuing hostname command yields the machine
> name not localhost)
> do you have any idea? could it be related to same machine as the master
> configuration?
>
> On Wed, Aug 17, 2011 at 6:59 PM, NerdyNick <ne...@gmail.com> wrote:
>>
>> So flume masters, collectors, and agent nodes should be registering
>> there physical name as whatever there hostname is, as returned by the
>> hostname command. That being said you can also create a logical node
>> and map it that way. You can also use physical DNS/IP's for the Agent
>> Sinks and Collector Source's. I currently do it this way as it allows
>> me to use multi master better, but does bring a slight layer of
>> confusion.
>>
>> As for the configuration, I don't see a massive problem with it as
>> long as you aren't planning to pump a very large amount of traffic at
>> it.
>>
>> On Wed, Aug 17, 2011 at 6:50 AM, Lior Harel <ha...@gmail.com> wrote:
>> > I have setup the collector to run on the same machine as the master.
>> > When
>> > running the collector as a daemon I couldn't find a way to specify its
>> > physical name and it always registers as localhost. So I'm not sure how
>> > to
>> > configure the agents' collectorSource, localhost?
>> > is there a way to specify a physical name for the daemon's node?
>> > also, I know this configuration (master + collector on the same machine)
>> > is
>> > considered pseudo distributed mode (for dev purposes mainly), assuming
>> > we
>> > roll out incrementally with limited number of events at the beginning,
>> > is
>> > this configuration reasonable?
>> >
>> > Thanks.
>>
>>
>>
>> --
>> Nick Verbeck - NerdyNick
>> ----------------------------------------------------
>> NerdyNick.com
>> Coloco.ubuntu-rocks.org
>
>

Re: set daemon physical name

Posted by Lior Harel <ha...@gmail.com>.
Thanks for the quick response, so I guess I'm having an issue here as the
node registers as localhost. (issuing hostname command yields the machine
name not localhost)
do you have any idea? could it be related to same machine as the master
configuration?

On Wed, Aug 17, 2011 at 6:59 PM, NerdyNick <ne...@gmail.com> wrote:

> So flume masters, collectors, and agent nodes should be registering
> there physical name as whatever there hostname is, as returned by the
> hostname command. That being said you can also create a logical node
> and map it that way. You can also use physical DNS/IP's for the Agent
> Sinks and Collector Source's. I currently do it this way as it allows
> me to use multi master better, but does bring a slight layer of
> confusion.
>
> As for the configuration, I don't see a massive problem with it as
> long as you aren't planning to pump a very large amount of traffic at
> it.
>
> On Wed, Aug 17, 2011 at 6:50 AM, Lior Harel <ha...@gmail.com> wrote:
> > I have setup the collector to run on the same machine as the master. When
> > running the collector as a daemon I couldn't find a way to specify its
> > physical name and it always registers as localhost. So I'm not sure how
> to
> > configure the agents' collectorSource, localhost?
> > is there a way to specify a physical name for the daemon's node?
> > also, I know this configuration (master + collector on the same machine)
> is
> > considered pseudo distributed mode (for dev purposes mainly), assuming we
> > roll out incrementally with limited number of events at the beginning, is
> > this configuration reasonable?
> >
> > Thanks.
>
>
>
> --
> Nick Verbeck - NerdyNick
> ----------------------------------------------------
> NerdyNick.com
> Coloco.ubuntu-rocks.org
>

Re: set daemon physical name

Posted by NerdyNick <ne...@gmail.com>.
So flume masters, collectors, and agent nodes should be registering
there physical name as whatever there hostname is, as returned by the
hostname command. That being said you can also create a logical node
and map it that way. You can also use physical DNS/IP's for the Agent
Sinks and Collector Source's. I currently do it this way as it allows
me to use multi master better, but does bring a slight layer of
confusion.

As for the configuration, I don't see a massive problem with it as
long as you aren't planning to pump a very large amount of traffic at
it.

On Wed, Aug 17, 2011 at 6:50 AM, Lior Harel <ha...@gmail.com> wrote:
> I have setup the collector to run on the same machine as the master. When
> running the collector as a daemon I couldn't find a way to specify its
> physical name and it always registers as localhost. So I'm not sure how to
> configure the agents' collectorSource, localhost?
> is there a way to specify a physical name for the daemon's node?
> also, I know this configuration (master + collector on the same machine) is
> considered pseudo distributed mode (for dev purposes mainly), assuming we
> roll out incrementally with limited number of events at the beginning, is
> this configuration reasonable?
>
> Thanks.



-- 
Nick Verbeck - NerdyNick
----------------------------------------------------
NerdyNick.com
Coloco.ubuntu-rocks.org