Vinod, hopefully it isn't too late for a quick fix to be included into 2.7.2
(sorry for jumping too late on this train). The JIRA in question is
HADOOP-12415 and I have committed it to trunk and branch-2 already.
Please let me know if this is still Ok to add into 2.7.2 as it seems to be
going thro
On Wed, Nov 25, 2015 at 01:51PM, Steve Loughran wrote:
>
> > On 25 Nov 2015, at 02:48, Konstantin Boudnik wrote:
> >
> > Vinod, hopefully it isn't too late for a quick fix to be included into 2.7.2
> > (sorry for jumping too late on this train). The JIRA in qu
ing the same.
>
> Thanks
> +Vinod
>
> > On Nov 27, 2015, at 1:54 AM, Steve Loughran wrote:
> >
> > well, I'm not going to block it...it doesn't add anything more to the pom
> > dependencies that aren't there right now
> >
> >>
I am looking into your log and see this
/usr/bin/build-classpath: error: Could not find jaxp_parser_impl Java
extension for this JVM
/usr/bin/build-classpath: error: Some specified jars were not found
Does it ring a bell?
Cos
On Thu, Jan 24, 2013 at 06:57PM, Brad Childs wrote:
> I'm trying to
The issue with the configuration is raised (and adressed) in
https://issues.apache.org/jira/browse/BIGTOP-841
Cos
On Fri, Feb 08, 2013 at 04:25PM, Aaron T. Myers wrote:
> +1 (binding)
>
> I downloaded the src tar ball, built it with the native bits enabled,
> started up a little cluster, and
We've created BigTop stack with 2.0.3 as the base. Ran YCSB, slive, and some
other loads on up to 20 nodes clusters as a part of the release validation.
Two issues were noted:
- due to the known issue with Jetty we are seeing MR jobs hanging here and
there
- without properly configured capacity-
On Tue, Feb 12, 2013 at 07:44PM, Konstantin Boudnik wrote:
> We've created BigTop stack with 2.0.3 as the base. Ran YCSB, slive, and some
> other loads on up to 20 nodes clusters as a part of the release validation.
> Two issues were noted:
>
> - due to the known issue with Je
On Thu, Feb 28, 2013 at 03:08PM, sanjay Radia wrote:
> +1
> Java has done the bulk of the work in making Hadoop multi-platform.
> Windows specific code is a tiny percentage of the code.
> Jeninks support for windows is going help us keep the platform portable going
> forward.
> I expect that the v
It seems that with the HW in place, the matter of setting at least nightly
build is trivial for anyone with up to date Windows knowledge. I wish I could
help. Going without a validation is a recipe for a disaster IMO.
-1 until some reasonable solution is implemented.
Cos
On Fri, Mar 01, 2013 at
Suresh, I appreciate all the troubles you're going through wrt syncing up the
huge patch for a long time - I really do.
I am not asking to have full test-patch process in place. But I think it is a
real good idea to have a way to run the full test suite once in a while - or
as Konstantin proposing
t; > Making two builds is less than 2 days work, imho, given that there is
> > a Windows node available and that mvn targets are in place. Correct me
> > if I missed any complications in the process.
>
> On Fri, Mar 1, 2013 at 3:47 PM, Konstantin Boudnik wrote:
> > It seems t
It doesn't look like any progress has been done on the ticket below in the
last 3 weeks. And now branch-2 can't be compiled because of
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestDFSShell.java:[895,15]
WINDOWS is not public in org.apache.hadoop.fs.Path; cannot be acce
ache.org/jira/browse/HDFS-4615?focusedCommentId=13612650&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13612650
>
> Regards,
> Suresh
>
>
> On Mon, Mar 25, 2013 at 1:17 PM, Konstantin Boudnik wrote:
>
> > It doesn't look like any progress
Here's a daily build for hadoop-2 branch
https://builds.apache.org/job/Hadoop-branch2
It just builds the full Hadoop project without running any tests (for now).
Can be easily extended to do test runs/artifact deployment, if needed.
Cos
On Mon, Mar 25, 2013 at 07:14PM, Konstantin Bo
I have split CLI test infrastructure into hierarchical pieces that allow to
have different configurations for different components. E.g. you can have one
for YARN that would exist independently of HDFS, etc. The change has been in
since like 0.22 and committed to 0.203.x as well IIRC, hence should
o track remote branch branch-0.22 from origin.
> Switched to a new branch 'branch-0.22'
> # find ./ -name *Conf.xml
> ./src/test/hdfs/org/apache/hadoop/cli/testHDFSConf.xml
>
>
> Maybe I'm missing something?
>
>
> On Thu, Apr 11, 2013 at 1:28 AM, Konst
-0
the release is missing HADOOP-9704 that has critical effect on downstream
projects e.g. build are affected. The issue has been raised for the first time
back in 4/10/13 http://is.gd/OGb3GG and never been even sneezed upon.
Cos
On Sat, Apr 13, 2013 at 03:26AM, Arun C Murthy wrote:
> Folks,
>
All,
I have created a release candidate (rc0) for hadoop-2.0.4.1-alpha that I would
like to release.
This is a stabilization release that includes fixed for a couple a of issues
discovered in the testing with BigTop 0.6.0 release candidate.
The RC is available at: http://people.apache.org/~cos/h
re very confusing. Some of them never been concluded, the
branches are moved and artifact versions seem to be colliding. 2.0.4.x seems
to work well for the stabilization purposes and it will allow to unblock
downstream and integration projects quickly.
Cos
> Arun
>
> On May 24, 2013, at 8:48 P
is the first time we are seeing a four-numbered scheme in
> > Hadoop. Why not call this 2.0.5-alpha?
>
> Good point. Since it contains only backports from branch-2, it would
> make sense for it to be an intermediate release.
>
> I shouldn't have to say this, but I&
On Thu, May 30, 2013 at 03:18PM, Chris Douglas wrote:
> On Thu, May 30, 2013 at 2:39 PM, Konstantin Boudnik wrote:
> > There's no misunderstanding Chris - this release is to unblock downstream.
> >
> > As for your question: I don't have a crystal ball; I wish thou
that's standard
> usage. Whoever makes the 2.0.5 release (or any "next" release) is expected
> to update the parent branch's SNAPSHOT default versioning, per
> HowToReleasePostMavenization#Branching<https://wiki.apache.org/hadoop/HowToReleasePostMavenization#Branching&
tml
>
> 0.17.2 was missing some native libs so 0.17.2.1 was released to fix
> that critical issue instead of calling it .3
Exactly the point - the _bigfix_ release. Thanks for pointing out the
similarities.
Cos
>
> J-D
>
> On Thu, May 30, 2013 at 3:52 PM, Konstantin Boudnik
On Thu, May 30, 2013 at 05:30PM, Chris Douglas wrote:
> On Thu, May 30, 2013 at 3:25 PM, Konstantin Boudnik wrote:
> > There's no plans to release anything else at this point - this is a bug-fix
> > release, as I pointed out on a numerous occasions. There's no new fe
urrent 2.0.5 version in JIRA to 2.1.0, create a new 2.0.5
> version, change the fix version of the 2 JIRAs that make the RC
>
> Thanks.
>
>
> On Thu, May 30, 2013 at 6:18 PM, Chris Douglas wrote:
>
> > On Thu, May 30, 2013 at 5:51 PM, Konstantin Boudnik
> > wr
o 2.0.5-alpha versions
> in jira for HADOOP, HDFS, YARN & MAPREDUCE.
>
> Please take care of the rest.
>
> Also, in branch-2, the version should be 2.1.0-SNAPSHOT.
>
> thanks,
> Arun
>
> >
> > Thanks.
> >
> >
> > On Thu, May 30, 20
Guys,
I will be performing some changes wrt to moving 2.0.4.1 release candidate to
2.0.5 space. As outline below by Alejandro:
1. I will create new 2.0.5-alpha branch from the current head of 2.0.4-alpha
that contains 2.0.4.1 changes
2. consequently, set the artifacts version on the new branch to
, 2013 at 12:45 PM, Konstantin Boudnik wrote:
>
> > Guys,
> >
> > I will be performing some changes wrt to moving 2.0.4.1 release candidate
> > to
> > 2.0.5 space. As outline below by Alejandro:
> >
> > 1. I will create new 2.0.5-alpha branch from the current
All,
I have created a release candidate (rc0) for hadoop-2.0.5-alpha that I would
like to release.
This is a stabilization release that includes fixed for a couple a of issues
discovered in the testing with BigTop 0.6.0 release candidate.
The RC is available at: http://people.apache.org/~cos/had
oes not have the 2.0.5-alpha section (it should
> be there empty).
>
> Cos, can you please look at these 2 things and explain/fix?
>
> Thanks.
>
>
>
> On Fri, May 31, 2013 at 4:04 PM, Konstantin Boudnik wrote:
>
> > All,
> >
> > I have create
that you guys have noted
earlier and will be re-spinning RC1 in a few.
Cos
On Fri, May 31, 2013 at 08:07PM, Konstantin Boudnik wrote:
> Alejandro,
>
> thanks for looking into this. Indeed - I missed the 2.0.5-alpha section in
> YARN CHANGES.txt. Added now. As for HDFS-4646: appare
All,
I have created a release candidate (rc1) for hadoop-2.0.5-alpha that I would
like to release.
This is a stabilization release that includes fixed for a couple a of issues
discovered in the testing with BigTop 0.6.0 release candidate.
The RC is available at: http://people.apache.org/~cos/had
Chris,
with 2.0.5-alpha (rc1) out, would you please take a look at the release bits?
I assume the four-digit numbering scheme issue has been resolved now.
Regards,
Cos
On Thu, May 30, 2013 at 06:18PM, Chris Douglas wrote:
> On Thu, May 30, 2013 at 5:51 PM, Konstantin Boudnik wrote:
&g
I changes are completed, I have updated branch-2 and trunk CHANGES.txt files
as planned. Version of the branch-2 is set to 2.1.0-beta; 2.0.5-alpha release
artifacts are deployed to the staging area.
Thanks for your patience, guys!
Cos
On Fri, May 31, 2013 at 12:45PM, Konstantin Boudnik wrote
ttp://people.apache.org/~cos/hadoop-2.0.5-alpha-rc1/
> > looks good to me.
> > +1 (non-binding)
> >
> > Thanks,
> >
> > Joep
> >
> >
> > On Fri, May 31, 2013 at 8:25 PM, Konstantin Boudnik
> > wrote:
> >
> > > Ok, WRT HDFS-
asy way to solve it it would be
> using as release date the date the vote ends. Anyway, not a big deal if we
> are not cutting a new rc for other reason
>
> +1 on rc1
>
> Thx
>
> On Jun 2, 2013, at 12:04 AM, Konstantin Boudnik wrote:
>
> > Alejandro,
> &
hes, ie branch-2 and trunk. Am I correct?
Thanks,
Cos
> hth,
> Arun
>
> On Jun 2, 2013, at 12:33 PM, Konstantin Boudnik wrote:
>
> > This is my first Hadoop release, so I am all ears ;) I looked at how Arun
> > was
> > cutting the previous 2.0.x and followed
out it I will alter the CHANGES.txt
files
thanks,
Cos
> Arun
>
> On Jun 2, 2013, at 6:41 PM, Konstantin Boudnik wrote:
>
> > On Sun, Jun 02, 2013 at 03:04PM, Arun C Murthy wrote:
> >> I record the 'release date' as the one on which the build is crea
Ok, if this the consensus on the issue, then tonight I will cut rc2 with only
CHANGES.txt release dates update. After that I will extend the vote once
again.
Sorry for the hassle to all who did voted before.
Cos
On Mon, Jun 03, 2013 at 12:18AM, Doug Cutting wrote:
> On Sun, Jun 2, 2013 at 9:01
te before 06/06/2013 5pm PDT.
Thanks for your patience!
Cos
On Fri, May 31, 2013 at 09:27PM, Konstantin Boudnik wrote:
> All,
>
> I have created a release candidate (rc1) for hadoop-2.0.5-alpha that I would
> like to release.
>
> This is a stabilization release that i
+1 [non-binding]:
checksums match, builds, and some simple tests are running ok.
On Thu, Apr 11, 2013 at 07:55PM, Thomas Graves wrote:
> I've created a release candidate (RC0) for hadoop-0.23.7 that I would like
> to release.
>
> This release is a sustaining release with several important bug f
signatures, built, ran
> single node cluster.
>
> Thanks,
> Tom
>
>
>
> On 6/3/13 2:51 PM, "Konstantin Boudnik" wrote:
>
> >I have rolled out release candidate (rc2) for hadoop-2.0.5-alpha.
> >
> >The difference between rc1 and rc2 is th
I am clearly +1 (non-binding) on the release.
With 8 +1s (3 binding), no -1s or 0s the vote passes.
Thanks to all who verified the bits, I'll push them out shortly.
Thanks,
Cos
On Mon, Jun 03, 2013 at 12:51PM, Konstantin Boudnik wrote:
> I have rolled out release candidate (rc2) fo
All,
I have created a release candidate (rc0) for hadoop-2.0.6-alpha that I would
like to release.
This is a stabilization release that includes fixed for a couple a of issues
as outlined on the security list.
The RC is available at: http://people.apache.org/~cos/hadoop-2.0.6-alpha-rc0/
The RC t
don't have license
> headers,
>
> I think we need to address the NO OK points (specially the last one), they
> are trivial.
>
> Thanks.
>
>
>
> On Sat, Aug 10, 2013 at 5:46 PM, Konstantin Boudnik wrote:
>
> > All,
> >
> > I have created
the NO OK points (specially the last one), they
> are trivial.
>
> Thanks.
>
>
>
> On Sat, Aug 10, 2013 at 5:46 PM, Konstantin Boudnik wrote:
>
> > All,
> >
> > I have created a release candidate (rc0) for hadoop-2.0.6-alpha that I
> > would
> &
:check passes on the RC before publishing
> it.
>
> Arun, as you are about to cut the new RC for 2.1.0-beta, can you please
> make sure the license headers are used in the releasenotes HTML files?
>
> Thx
>
>
> On Thu, Aug 15, 2013 at 8:02 PM, Konstantin
All,
I have created a release candidate (rc1) for hadoop-2.0.6-alpha that I would
like to release.
This is a stabilization release that includes fixed for a couple a of issues
as outlined on the security list.
The RC is available at: http://people.apache.org/~cos/hadoop-2.0.6-alpha-rc1/
The RC t
I am clearly +1 (non-binding) on the release.
With 8 +1s (5 binding), no -1s or 0s the vote passes.
Thanks to all who verified the bits, I'll push them out shortly.
Thanks,
Cos
On Thu, Aug 15, 2013 at 10:29PM, Konstantin Boudnik wrote:
> All,
>
> I have created a release candi
All,
I have pushed the bits of 2.0.6-alpha into the open and released staging bits
in Nexus. Site is updated with the release news.
2.0.6-alpha is officially live now. Thanks everybody for your help!
Cos
On Thu, Aug 22, 2013 at 11:09PM, Konstantin Boudnik wrote:
> I am clearly +1 (
On Thu, Mar 22, 2012 at 10:25AM, Eli Collins wrote:
> On Thu, Mar 22, 2012 at 1:26 AM, Konstantin Shvachko
> wrote:
> > Eli,
> >
> > I went over the entire discussion on the topic, and did not get it. Is
> > there a problem with append? We know it does not work in hadoop-1,
> > only flush() does.
On Thu, Mar 22, 2012 at 03:22PM, Eli Collins wrote:
> On Thu, Mar 22, 2012 at 3:11 PM, Konstantin Boudnik wrote:
> > On Thu, Mar 22, 2012 at 10:25AM, Eli Collins wrote:
> >> On Thu, Mar 22, 2012 at 1:26 AM, Konstantin Shvachko
> >> wrote:
> >> > El
TLDR :/
Besides, it isn't a job list
Cos
On Mon, Apr 09, 2012 at 10:59PM, Bing Li wrote:
> 国际著名大型IT企业（排名前3位）开发中心招聘Hadoop技术专家（北京）-非猎头
>
> 职位描述：
> Hadoop系统和平台开发（架构师，资深开发人员）
>
>
> 职位要求：
>
> 1.有设计开发大型分布式系统的经验（工作年限3年以上，架构师5年以上），hadoop大型实际应用经验优先
>
> 2.良好的编程和调试经验(java or c++/c)，扎实的计算机理论基础，快速的学习能力
On Wed, Sep 26, 2012 at 04:17PM, Konstantin Shvachko wrote:
> Hi Todd,
>
> > I had said previously that it's worth
> > discussing if several other people believe the same.
>
> Well let's put it on to general list for discussion then?
> Seems to me an important issue for Hadoop evolution in gener
On Wed, May 18, 2016 at 08:29AM, Allen Wittenauer wrote:
> That’s really a question for infrastructure-...@apache.org . They
> manage the ASF build infrastructure which Apache Hadoop and lots of
> other projects utilize. (Bigtop uses something custom, which I think
> is fun
Do you guys think that committing
https://issues.apache.org/jira/browse/HDFS-4858
to branch-2.3 is still Ok? It is a small change that bring fixes broken
timeout behavior of DN to NN RPC.
We have been testing this fix on top of 2.0.6 for a long time now and it seems
to be a real help.
Apprec
Guys,
In the last a couple of weeks, we had a very good and productive initial round
of discussions on the JIRAs. I think it is worthy to keep the momentum going
and have a more detailed conversation. For that, we'd like to host s Hadoop
developers meetup to get into the bowls of the consensus-bas
They are actually listed in the first email on this thread. Here they are:
HADOOP-10641
HDFS-6469
Cos
On Wed, Jun 18, 2014 at 10:30PM, Sujeet Varakhedi wrote:
> Can you point me to the JIRA's
>
> Sujeet
>
>
> On Wed, Jun 18, 2014 at 8:45 PM, Konstantin Boud
2014 at 08:45PM, Konstantin Boudnik wrote:
> Guys,
>
> In the last a couple of weeks, we had a very good and productive initial round
> of discussions on the JIRAs. I think it is worthy to keep the momentum going
> and have a more detailed conversation. For that, we'd like to host s Had
All,
Re-sending this announcement in case it fell through over the long weekend
when people were away. We still have seats left, so register soon.
Regards,
Cos
On Wed, Jul 02, 2014 at 06:37PM, Konstantin Boudnik wrote:
> We'd like to invite you to the
> Consensus based rep
ctly to me if you're interested before end of Sunday, 13th.
Cheers,
Cos
On Tue, Jul 08, 2014 at 12:23PM, Konstantin Boudnik wrote:
> All,
>
> Re-sending this announcement in case it fell through over the long weekend
> when people were away. We still have seats left, so register
1-919
=
BTW, we have one or two spots left, so if you didn't make your reservation -
now is the time.
See you all tomorrow.
Cos
On Fri, Jul 11, 2014 at 04:33PM, Konstantin Boudnik wrote:
> One more update: it seema that for ppl in SF, who oftentimes might not even
> So, IMO, the goal should be the examples on 10-24 or 31-36.
+1 I agree with Todd: the highlighted snippets are most appropriate as Java
coding style.
On 11/20/09 10:54 , Todd Lipcon wrote:
My opinions on the groups of line numbers from that pastebin:
1-3: Definitely not - no reason for ) o
Sanjay.
the generation of the .classpath file has been a pain-point for everybody
committing the code and making dependecy changes in Hadoop.
Everytime new jar has been added to the project one should've remember to
update Eclipse deps even if that person doesn't use that IDE. Otherwise,
Eclipse
That's might be the case. I will take a look at this first thing Monday
On Fri, Jan 7, 2011 at 16:32, Nigel Daley wrote:
>> [junit] Test org.apache.hadoop.hdfsproxy.TestHdfsProxy FAILED
>> ...
>> /grid/0/hudson/hudson-slave/workspace/Hadoop-Hdfs-21-Build/trunk/src/contrib/hdfsproxy/build.xml:
Moving hdfs-dev@ and mapreduce-dev@ to Bcc: to avoid cross-postings.
>From what I understand you want to have a test case which demonstrates
that whatever socket/stream connections were opened are properly
closed in case of IOException? I guess one of many possibilities would
be to check if a conn
JIRA has this nice feature called 'Tag'. We've been using this for
Herriot development - seems much cleaner than clogging synopses field
with additional wodking.
--
Take care,
Konstantin (Cos) Boudnik
On Fri, Feb 25, 2011 at 14:53, Todd Lipcon wrote:
> Hey folks,
>
> Would those of you workin
;HDFS Federation". As far as tagging is concerned,
> all federation jiras are subtasks of HDFS-1052. Hence some kind of grouping
> can be done based on that.
>
> On Fri, Feb 25, 2011 at 4:28 PM, Konstantin Boudnik wrote:
>
>> JIRA has this nice feature called 'Tag
I have took a look at the test and I should note that the way they written if
kinda misleading. For instance the message we are seeing in the Hudson says
expected:<403> but was:<200>
where's the reality is that the expected was <200> and actual value was <403>.
Basically the order of assert cal
In spite of this alleged abandonment would it be desirable to
reconsider late decision about removing hdfsproxy away from hdfs
project?
--
Cos
On Mon, Apr 4, 2011 at 10:14, Todd Lipcon wrote:
> Hi all,
>
> The hdfsproxy TestAuthorizationFilter test has been failing now for quite a
> long time.
Sanjay,
I assume the outlined changes won't an earlier version of HDFS from
upgrads to the federation version, right?
Cos
On Tue, Apr 26, 2011 at 17:26, Sanjay Radia wrote:
>
> Changes to the code base
> - The fundamental code change is to extend the notion of block id to now
> include a block
Oops, the message came out garbled. I meant to say
I assume the outlined changes won't prevent an earlier version of HDFS from
upgrades to the federation version, right?
Thanks in advance,
Cos
On Tue, Apr 26, 2011 at 17:59, Konstantin Boudnik wrote:
> Sanjay,
>
> I assum
Interesting... while the read performance has only marginally improved
<4% (still a good thing) the write performance shows significantly
better improvements >10%. Very interesting asymmetry, indeed.
Suresh, what was the size of the cluster in the testing?
Cos
On Wed, Apr 27, 2011 at 10:02, sur
+1. Having an open QE process would be a tremendous value-add to the
overall quality of the feature. Append was an exemplary development in
this sense. Would it be possible to have Federation test plan (if
exists) to be published along with the specs on the JIRA (similar to
HDFS-265) at least for t
I see that the whole AOP stuff has been taken out along with Herriot work.
I don't see any discussion about this on the JIRA. Neither I don't see any
tickets created to track the effort (but a subtask for FI tests in
HADOOP-7412).
Any reason we are missing a big chunk of validation infrastructure
oop, I guess you are the best person to
> take care of this part of the puzzle.
>
> Thanks.
>
> Alejandro
>
> On Fri, Aug 19, 2011 at 11:09 AM, Konstantin Boudnik wrote:
>
> > I see that the whole AOP stuff has been taken out along with Herriot work.
> > I d
[
https://issues.apache.org/jira/browse/HDFS-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved HDFS-2442.
--
Resolution: Won't Fix
Release Note: This has been resolved in Bigtop for a
[
https://issues.apache.org/jira/browse/HDFS-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik reopened HDFS-4269:
--
Reopening to merge into branch-2
> DatanodeManager#registerDatan
[
https://issues.apache.org/jira/browse/HDFS-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved HDFS-4269.
--
Resolution: Fixed
Committed to branch-2. Thanks Chris
[
https://issues.apache.org/jira/browse/HDFS-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved HDFS-4600.
--
Resolution: Invalid
The issues seems to be caused by specific cluster configuration
[
https://issues.apache.org/jira/browse/HDFS-6471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved HDFS-6471.
--
Resolution: Fixed
Release Note: Committed to trunk and merged into branch-2
[
https://issues.apache.org/jira/browse/HDFS-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik deleted HDFS-437:
> Folder .eclipse.templates is missed from new HDFS t
Folder .eclipse.templates is missed from new HDFS tree
--
Key: HDFS-437
URL: https://issues.apache.org/jira/browse/HDFS-437
Project: HDFS
Issue Type: Bug
Reporter: Konstantin
/jira/browse/HDFS-444
Project: HDFS
Issue Type: Sub-task
Reporter: Konstantin Boudnik
Assignee: Konstantin Boudnik
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
: Bug
Components: test
Affects Versions: 0.20.1
Reporter: Konstantin Boudnik
Using FI framework (HADOOP-6003) I'm injecting some faults into BlockReceiver
class. When DiskOutOfSpaceException is thrown at at BlockReceiver.java:449 it
causes the very first test ca
-task
Reporter: Konstantin Boudnik
Assignee: Konstantin Boudnik
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[
https://issues.apache.org/jira/browse/HDFS-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved HDFS-476.
-
Resolution: Duplicate
It duplicates HDFS-475
> Create a fi test tar
---
Key: HDFS-493
URL: https://issues.apache.org/jira/browse/HDFS-493
Project: Hadoop HDFS
Issue Type: Improvement
Components: build, test
Reporter: Konstantin Boudnik
Assignee: Konstantin Boudnik
New fault
Boudnik
Assignee: Konstantin Boudnik
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
adoop HDFS
Issue Type: Improvement
Components: build, test
Reporter: Konstantin Boudnik
This issue is created to track the conversion of external testlist for 10
minutes tests into JUnit test suite.
It would be consistent through the bigger Hadoop project to ha
[
https://issues.apache.org/jira/browse/HDFS-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved HDFS-505.
-
Resolution: Won't Fix
> Convert the file including 10 minutes run's tests
orter: Konstantin Boudnik
According to the test plan a number of new features are going to be implemented
as a part of this umbrella (HDFS-265) JIRA.
These new features are have to be tested properly. hflush is one of new
functionality which require new tests to be developed.
--
This message is automati
Create new tests for lease recovery
---
Key: HDFS-519
URL: https://issues.apache.org/jira/browse/HDFS-519
Project: Hadoop HDFS
Issue Type: Sub-task
Reporter: Konstantin Boudnik
--
This
Create new tests for block recovery
---
Key: HDFS-520
URL: https://issues.apache.org/jira/browse/HDFS-520
Project: Hadoop HDFS
Issue Type: Sub-task
Reporter: Konstantin Boudnik
--
This
Create new tests for pipeline
-
Key: HDFS-521
URL: https://issues.apache.org/jira/browse/HDFS-521
Project: Hadoop HDFS
Issue Type: Sub-task
Reporter: Konstantin Boudnik
--
This message is
Create stress tests for append feature
--
Key: HDFS-522
URL: https://issues.apache.org/jira/browse/HDFS-522
Project: Hadoop HDFS
Issue Type: Sub-task
Reporter: Konstantin Boudnik
--
This
: Konstantin Boudnik
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
: test
Reporter: Konstantin Boudnik
Clearly, TestFileAppend* were created in a copy-cat mode which produces a
number of duplications.
As more tests for the new append feature are going to be developed, I'd like to
get rid of these duplications and allow some a better code
Project: Hadoop HDFS
Issue Type: Improvement
Components: test
Reporter: Konstantin Boudnik
Assignee: Konstantin Boudnik
Attachments: HDFS-539.patch
It turns out that the current version of the helper classes introduced by
HDFS-451
: Hadoop HDFS
Issue Type: Improvement
Reporter: Konstantin Boudnik
It is currently impossible to run non fault-injection tests with fault-injected
build. E.g.
{noformat}
ant run-test-hdfs-fault-inject -Dtestcase=TestFileCreation
{noformat}
because {{macro-test-runner
1 - 100 of 223 matches
Mail list logo
