Vitalii Tymchyshyn skrev:
01.09.11 21:55, Per Steffensen написав(ла):
Vitalii Tymchyshyn skrev:
Hello.
AFAIK now you still have HDFS NameNode and as soon as NameNode is
down - your cluster is down. So, putting scheduling on the same
machine as NameNode won't make you cluster worse in terms o
01.09.11 21:55, Per Steffensen написав(ла):
Vitalii Tymchyshyn skrev:
Hello.
AFAIK now you still have HDFS NameNode and as soon as NameNode is
down - your cluster is down. So, putting scheduling on the same
machine as NameNode won't make you cluster worse in terms of SPOF (at
least for HW fa
I will be able to run e.g. MapReduce
jobs even if 3 of the 10 machines are down. I want my timer framework
to also be clustered, distributed and coordinated, so that I will
also have my timer jobs triggered even though 3 out of 10 machines
are down.
Hello.
AFAIK now you still have HDFS NameN
MapReduce jobs
even if 3 of the 10 machines are down. I want my timer framework to
also be clustered, distributed and coordinated, so that I will also
have my timer jobs triggered even though 3 out of 10 machines are down.
Hello.
AFAIK now you still have HDFS NameNode and as soon as NameNo
12:30 PM, Per Steffensen
>>>> wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> Hi
>>>>>
>>>>> I use hadoop for a MapReduce job in my system. I would like to have the
>>>>> job
re down. I want my timer framework to also be
clustered, distributed and coordinated, so that I will also have my
timer jobs triggered even though 3 out of 10 machines are down.
Regards, Per Steffensen
Ronen Itkin skrev:
If I get you right you are asking about Installing Oozie as Distributed
;>> Ronen Itkin skrev:
>>>>
>>>> Hi
>>>>
>>>>
>>>>> Try to use Oozie for job coordination and work flows.
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Sep 1, 2011 at 12:30 PM, Per Steffe
ramework (CRON or
something like that) that invokes the MapReduce job. But CRON is only
running on one particular machine, so if that machine goes down my job
will
not be triggered. Then I could setup the timer on all or many machines,
but
I would not like the job to be run in more than one instance
t; >>> hadoop?
> >>> Of course I could setup a timer in an external timer framework (CRON or
> >>> something like that) that invokes the MapReduce job. But CRON is only
> >>> running on one particular machine, so if that machine goes down my job
> >>
Are there any "distributed" timer job stuff in
>>> hadoop?
>>> Of course I could setup a timer in an external timer framework (CRON or
>>> something like that) that invokes the MapReduce job. But CRON is only
>>> running on one particular machine, so
o be run in more than one instance every 5th
minute, so then the timer jobs would need to coordinate who is actually
starting the job "this time" and all the rest would just have to do nothing.
Guess I could come up with a solution to that - e.g. writing some "lock"
stuff using
r many machines, but
> I would not like the job to be run in more than one instance every 5th
> minute, so then the timer jobs would need to coordinate who is actually
> starting the job "this time" and all the rest would just have to do nothing.
> Guess I could come up with a s
t CRON
is only running on one particular machine, so if that machine goes down
my job will not be triggered. Then I could setup the timer on all or
many machines, but I would not like the job to be run in more than one
instance every 5th minute, so then the timer jobs would need to
coordin
13 matches
Mail list logo
