> >>> NOTICE: This message is intended for the use of the individual or
> >>>entity to
> >>> which it is addressed and may contain information that is confidential,
> >>> privileged and exempt from disclosure under applicable law. If the
> >>>reader
> >>> of this message is not the intended recipient, you are hereby notified
> >>>that
> >>> any printing, copying, dissemination, distribution, disclosure or
> >>> forwarding of this communication is strictly prohibited. If you have
> >>> received this communication in error, please contact the sender
> >>>immediately
> >>> and delete it from your system. Thank You.
> >>
> >>
> >
>
>
--
Have a Nice Day!
Lohit
idential,
> > > privileged and exempt from disclosure under applicable law. If the
> reader
> > > of this message is not the intended recipient, you are hereby notified
> > that
> > > any printing, copying, dissemination, distribution, disclosure or
> > > forwarding of this communication is strictly prohibited. If you have
> > > received this communication in error, please contact the sender
> > immediately
> > > and delete it from your system. Thank You.
> > >
> >
>
--
Have a Nice Day!
Lohit
+1 to merge into branch2 now.
On Jan 5, 2014 6:22 PM, "Zhijie Shen" wrote:
> Hi folks,
>
> Majority of the functionality of Application History Server has been
> completed on branch YARN-321. AHS can now work end-to-end. ResourceManager
> records the historical information of the application, the
[
https://issues.apache.org/jira/browse/YARN-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu resolved YARN-546.
---
Resolution: Duplicate
Resolving duplicate of YARN-1383
[
https://issues.apache.org/jira/browse/YARN-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu resolved YARN-290.
---
Resolution: Duplicate
Closing, duplicate of YARN-282
> Wrong cluster metr
ibe the cluster?
>
>
>
--
Have a Nice Day!
Lohit
Lohit Vijayarenu created YARN-1122:
--
Summary: FairScheduler user-as-default-queue always defaults to
'default'
Key: YARN-1122
URL: https://issues.apache.org/jira/browse/YARN-1122
Proje
Lohit Vijayarenu created YARN-1032:
--
Summary: NPE in RackResolve
Key: YARN-1032
URL: https://issues.apache.org/jira/browse/YARN-1032
Project: Hadoop YARN
Issue Type: Bug
Affects
[
https://issues.apache.org/jira/browse/YARN-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu resolved YARN-356.
---
Resolution: Invalid
> Add YARN_NODEMANAGER_OPTS and YARN_RESOURCEMANAGER_OPTS to yarn.
[
https://issues.apache.org/jira/browse/YARN-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu resolved YARN-307.
---
Resolution: Invalid
Resolving as wont invalid
> NodeManager should
Lohit Vijayarenu created YARN-546:
-
Summary: mapred.fairscheduler.eventlog.enabled removed from Hadoop
2.0
Key: YARN-546
URL: https://issues.apache.org/jira/browse/YARN-546
Project: Hadoop YARN
Lohit Vijayarenu created YARN-502:
-
Summary: RM crash with NPE on NODE_REMOVED event
Key: YARN-502
URL: https://issues.apache.org/jira/browse/YARN-502
Project: Hadoop YARN
Issue Type: Bug
Lohit Vijayarenu created YARN-451:
-
Summary: Add more metrics to RM page
Key: YARN-451
URL: https://issues.apache.org/jira/browse/YARN-451
Project: Hadoop YARN
Issue Type: Improvement
-requests have higher priority anyway.
>
> hth,
> Arun
>
> On Feb 25, 2013, at 1:03 PM, lohit wrote:
>
> > Hi Devs,
> >
> > With YARN, is there a way to limit max number of map tasks per cluster.
> For
> > example, if we have thousands of jobs running we
Lohit Vijayarenu created YARN-402:
-
Summary: Dispatcher warn message is too late
Key: YARN-402
URL: https://issues.apache.org/jira/browse/YARN-402
Project: Hadoop YARN
Issue Type
tc.
> > > Also YARN has achieved significant stability at scale (more details
> from
> > > Y! folks here: http://s.apache.org/VYO).
> > >
> > > The RC is available at:
> > > http://people.apache.org/~acmurthy/hadoop-2.0.3-alpha-rc0/
> > > The RC tag in svn is here:
> > >
> http://svn.apache.org/viewvc/hadoop/common/tags/release-2.0.3-alpha-rc0/
> > >
> > > The maven artifacts are available via repository.apache.org.
> > >
> > > Please try the release and vote; the vote will run for the usual 7
> days.
> > >
> > > thanks,
> > > Arun
> > >
> > >
> > >
> > > --
> > > Arun C. Murthy
> > > Hortonworks Inc.
> > > http://hortonworks.com/
> > >
> > >
> > >
>
--
Have a Nice Day!
Lohit
Lohit Vijayarenu created YARN-356:
-
Summary: Add YARN_NODEMANAGER_OPTS and YARN_RESOURCEMANAGER_OPTS
to yarn.env
Key: YARN-356
URL: https://issues.apache.org/jira/browse/YARN-356
Project: Hadoop YARN
[
https://issues.apache.org/jira/browse/YARN-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu resolved YARN-351.
---
Resolution: Duplicate
Thanks [~sandyr]. It does looks like it is solved in YARN-335. I was
Lohit Vijayarenu created YARN-351:
-
Summary: ResourceManager NPE during allocateNodeLocal
Key: YARN-351
URL: https://issues.apache.org/jira/browse/YARN-351
Project: Hadoop YARN
Issue Type
[
https://issues.apache.org/jira/browse/YARN-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu resolved YARN-287.
---
Resolution: Invalid
Thanks for explanation. Closing as invalid
> NodeMana
Lohit Vijayarenu created YARN-324:
-
Summary: Provide way to preserve
Key: YARN-324
URL: https://issues.apache.org/jira/browse/YARN-324
Project: Hadoop YARN
Issue Type: Bug
mapreduce.jobtracker.split.metainfo.maxsize to higher value I
could get the job running.
I will open JIRA for this.
2013/1/7 Lohit
> It is easily reproducible. Generate 10 TB of input data using
> teragen(replication 3) and try to run terasort using that input. First
> container fails without any informatio
It is easily reproducible. Generate 10 TB of input data using
teragen(replication 3) and try to run terasort using that input. First
container fails without any information in logs and job fails
Lohit
On Jan 7, 2013, at 6:41 AM, Robert Evans wrote:
> We have run some very large jobs on
Lohit Vijayarenu created YARN-307:
-
Summary: NodeManager should log container launch command.
Key: YARN-307
URL: https://issues.apache.org/jira/browse/YARN-307
Project: Hadoop YARN
Issue
Lohit Vijayarenu created YARN-305:
-
Summary: Too many 'Node offerred to app:..." messages in RM
Key: YARN-305
URL: https://issues.apache.org/jira/browse/YARN-305
Project: Hadoop YARN
Lohit Vijayarenu created YARN-290:
-
Summary: Wrong cluster metrics on RM page
Key: YARN-290
URL: https://issues.apache.org/jira/browse/YARN-290
Project: Hadoop YARN
Issue Type: Bug
Lohit Vijayarenu created YARN-287:
-
Summary: NodeManager logs incorrect physical/virtual memory values
Key: YARN-287
URL: https://issues.apache.org/jira/browse/YARN-287
Project: Hadoop YARN
Thanks Sandy, this worked.
2012/12/14 Sandy Ryza
> Hi Lohit,
>
> Setting yarn.scheduler.fair.assignmultiple to false should give a more even
> distribution of tasks.
>
> -Sandy
>
> On Fri, Dec 14, 2012 at 10:22 AM, lohit
> wrote:
>
> > I should
1 for your
> CapacityScheduler (are you using this or the Fifo)?
>
> On Fri, Dec 14, 2012 at 1:37 AM, lohit wrote:
> > I am running hadoop-2.0.3 alpha branch.
> > Right now I am trying TestDFSIO, where I would like to have even
> > distribution of tasks.
> > As
hat version of YARN?
>
> Tom
>
> On 12/13/12 12:24 AM, "lohit" wrote:
>
> >Hi Devs,
> >
> >I am running few experiments on YARN. On a 50 node cluster I run only one
> >job.
> >If I kick off job with 150 tasks, I would expect on an average 3 tasks
30 matches
Mail list logo
