Re: [Hadoop-3.3 Release update]- branch-3.3 has created

[Mingliang Liu]

Brahma,

What about https://issues.apache.org/jira/browse/HADOOP-17007?

Thanks,

On Fri, Apr 24, 2020 at 11:07 AM Brahma Reddy Battula 
wrote:

> Ok. Done. Branch created.
>
> Following blockers are pending, will closely track this.
>
> https://issues.apache.org/jira/browse/HDFS-15287 ( Open: Under discussion
> )
> https://issues.apache.org/jira/browse/YARN-10194 ( Patch Available)
> https://issues.apache.org/jira/browse/HDFS-15286 ( Patch Available)
> https://issues.apache.org/jira/browse/YARN-9898 ( Patch Available)
>
>
> On Fri, Apr 24, 2020 at 7:42 PM Wei-Chiu Chuang
>  wrote:
>
> > +1 we should have the branch ASAP.
> >
> > On Wed, Apr 22, 2020 at 11:07 PM Akira Ajisaka 
> > wrote:
> >
> > > > Since blockers are not closed, I didn't cut the branch because
> > > multiple branches might confuse or sombody might miss to commit.
> > >
> > > The current situation is already confusing. The 3.3.1 version already
> > > exists in JIRA, so some committers wrongly commit non-critical issues
> to
> > > branch-3.3 and set the fix version to 3.3.1.
> > > I think now we should cut branch-3.3.0 and freeze source code except
> the
> > > blockers.
> > >
> > > -Akira
> > >
> > > On Tue, Apr 21, 2020 at 3:05 PM Brahma Reddy Battula <
> bra...@apache.org>
> > > wrote:
> > >
> > >> Sure, I will do that.
> > >>
> > >> Since blockers are not closed, I didn't cut the branch because
> > >> multiple branches might confuse or sombody might miss to commit.Shall
> I
> > >> wait till this weekend to create..?
> > >>
> > >> On Mon, Apr 20, 2020 at 11:57 AM Akira Ajisaka 
> > >> wrote:
> > >>
> > >>> Hi Brahma,
> > >>>
> > >>> Thank you for preparing the release.
> > >>> Could you cut branch-3.3.0? I would like to backport some fixes for
> > >>> 3.3.1 and not for 3.3.0.
> > >>>
> > >>> Thanks and regards,
> > >>> Akira
> > >>>
> > >>> On Fri, Apr 17, 2020 at 11:11 AM Brahma Reddy Battula <
> > bra...@apache.org>
> > >>> wrote:
> > >>>
> >  Hi All,
> > 
> >  we are down to two blockers issues now (YARN-10194 and YARN-9848)
> > which
> >  are in patch available state.Hopefully we can out the RC soon.
> > 
> >  thanks to @Prabhu Joseph 
> > ,@masakate,@akira
> >  and @Wei-Chiu Chuang   and others for helping
> >  resloving the blockers.
> > 
> > 
> > 
> >  On Tue, Apr 14, 2020 at 10:49 PM Brahma Reddy Battula <
> >  bra...@apache.org> wrote:
> > 
> > >
> > > @Prabhu Joseph 
> > > >>> Have committed the YARN blocker YARN-10219 to trunk and
> > > cherry-picked to branch-3.3. Right now, there are two blocker
> Jiras -
> > > YARN-10233 and HADOOP-16982
> > > which i will help to review and commit. Thanks.
> > >
> > > Looks you committed YARN-10219. Noted YARN-10233 and HADOOP-16982
> as
> > a
> > > blockers. (without YARN-10233 we have given so many releases,it's
> > not newly
> > > introduced.).. Thanks
> > >
> > > @Vinod Kumar Vavilapalli  ,@adam Antal,
> > >
> > > I noted YARN-9848 as a blocker as you mentioned above.
> > >
> > > @All,
> > >
> > > Currently following four blockers are pending for 3.3.0 RC.
> > >
> > > HADOOP-16963,YARN-10233,HADOOP-16982 and YARN-9848.
> > >
> > >
> > >
> > > On Tue, Apr 14, 2020 at 8:11 PM Vinod Kumar Vavilapalli <
> > > vino...@apache.org> wrote:
> > >
> > >> Looks like a really bad bug to me.
> > >>
> > >> +1 for revert and +1 for making that a 3.3.0 blocker. I think
> should
> > >> also revert it in a 3.2 maintenance release too.
> > >>
> > >> Thanks
> > >> +Vinod
> > >>
> > >> > On Apr 14, 2020, at 5:03 PM, Adam Antal <
> adam.an...@cloudera.com
> > .INVALID>
> > >> wrote:
> > >> >
> > >> > Hi everyone,
> > >> >
> > >> > Sorry for coming a bit late with this, but there's also one jira
> > >> that can
> > >> > have potential impact on clusters and we should talk about it.
> > >> >
> > >> > Steven Rand found this problem earlier and commented to
> > >> > https://issues.apache.org/jira/browse/YARN-4946.
> > >> > The bug has impact on the RM state store: the RM does not delete
> > >> apps - see
> > >> > more details in his comment here:
> > >> >
> > >>
> >
> https://issues.apache.org/jira/browse/YARN-4946?focusedCommentId=16898599=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16898599
> > >> > .
> > >> > (FYI He also created
> > >> https://issues.apache.org/jira/browse/YARN-9848 with
> > >> > the revert task).
> > >> >
> > >> > It might not be an actual blocker, but since there wasn't any
> > >> consensus
> > >> > about a follow up action, I thought we should decide how to
> > proceed
> > >> before
> > >> > release 3.3.0.
> > >> >
> > >> > Regards,
> > >> > Adam
> > >> >
> > >> > On Tue, Apr 14, 2020 at 9:35 AM Prabhu Joseph <
> > >> 

[jira] [Resolved] (HADOOP-17013) this bug is bla bla bla

[Mingliang Liu (Jira)]

 [ 
https://issues.apache.org/jira/browse/HADOOP-17013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mingliang Liu resolved HADOOP-17013.

   Fix Version/s: (was: 0.24.0)
Target Version/s:   (was: 3.2.1)
  Resolution: Invalid

This is not fun [~islam.saied]. Please stop doing this. 

> this bug is bla bla bla
> ---
>
> Key: HADOOP-17013
> URL: https://issues.apache.org/jira/browse/HADOOP-17013
> Project: Hadoop Common
>  Issue Type: Bug
>  Components: bin
>Affects Versions: 3.2.1
>Reporter: islam
>Priority: Major
>  Labels: bulk-closed
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

Re: Hadoop 3.1.4 Release Code Freeze

[Wei-Chiu Chuang]

Gabor, can you also create the dot release branch so folks can start
cherrypicking commits for 3.1.5? Thank you

On Wed, Apr 22, 2020 at 3:54 AM Gabor Bota  wrote:

> Hi All,
>
> The code freeze for Hadoop 3.1.4 release is planned for today. There
> some issues still open for that version.
>
> These are the open issues with 3.1.4 target/fix version:
> * https://issues.apache.org/jira/browse/YARN-8234
> * https://issues.apache.org/jira/browse/HDFS-15205
> * https://issues.apache.org/jira/browse/HADOOP-16341
> * https://issues.apache.org/jira/browse/HDFS-15272
> * https://issues.apache.org/jira/browse/HADOOP-16193
> * https://issues.apache.org/jira/browse/YARN-8257
> * https://issues.apache.org/jira/browse/YARN-8417
> * https://issues.apache.org/jira/browse/HADOOP-16917
>
> Please check if your issue is a blocker. I will move these issues to
> 3.1.5 target/fix version after 04.23. 10AM CET. I also commented on
> each issue separately.
>
> Release info:
> * https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+3.1+Release
> * https://cwiki.apache.org/confluence/display/HADOOP/Roadmap
>
> Regards,
> Gabor
>
> -
> To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
>
>

[jira] [Created] (HADOOP-17013) this bug is bla bla bla

[islam (Jira)]

islam created HADOOP-17013:
--

 Summary: this bug is bla bla bla
 Key: HADOOP-17013
 URL: https://issues.apache.org/jira/browse/HADOOP-17013
 Project: Hadoop Common
  Issue Type: Bug
  Components: bin
Affects Versions: 3.2.1
Reporter: islam
 Fix For: 0.24.0






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

Re: Reverted YARN-10063 from branch-3.2

[Wei-Chiu Chuang]

Not a problem! I was just sending it out in case someone else was working
on the branch as well and wondering why.

On Thu, Apr 23, 2020 at 5:38 PM Wilfred Spiegelenburg
 wrote:

> Sorry for that, I had reverted it I thought but either I did not push or
> the push failed.
> I just checked and my local branch-3.2 had the revert in it dated about 2
> hours after the original commit.
>
> Wilfred
>
> > On 24 Apr 2020, at 05:52, Wei-Chiu Chuang 
> wrote:
> >
> > It broke the build (see here  >)
> > so revert the commit. Looks like it was unintentional.
>
>
> -
> To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
> For additional commands, e-mail: common-dev-h...@hadoop.apache.org
>
>

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

[Brahma Reddy Battula]

Ok. Done. Branch created.

Following blockers are pending, will closely track this.

https://issues.apache.org/jira/browse/HDFS-15287 ( Open: Under discussion )
https://issues.apache.org/jira/browse/YARN-10194 ( Patch Available)
https://issues.apache.org/jira/browse/HDFS-15286 ( Patch Available)
https://issues.apache.org/jira/browse/YARN-9898 ( Patch Available)


On Fri, Apr 24, 2020 at 7:42 PM Wei-Chiu Chuang
 wrote:

> +1 we should have the branch ASAP.
>
> On Wed, Apr 22, 2020 at 11:07 PM Akira Ajisaka 
> wrote:
>
> > > Since blockers are not closed, I didn't cut the branch because
> > multiple branches might confuse or sombody might miss to commit.
> >
> > The current situation is already confusing. The 3.3.1 version already
> > exists in JIRA, so some committers wrongly commit non-critical issues to
> > branch-3.3 and set the fix version to 3.3.1.
> > I think now we should cut branch-3.3.0 and freeze source code except the
> > blockers.
> >
> > -Akira
> >
> > On Tue, Apr 21, 2020 at 3:05 PM Brahma Reddy Battula 
> > wrote:
> >
> >> Sure, I will do that.
> >>
> >> Since blockers are not closed, I didn't cut the branch because
> >> multiple branches might confuse or sombody might miss to commit.Shall I
> >> wait till this weekend to create..?
> >>
> >> On Mon, Apr 20, 2020 at 11:57 AM Akira Ajisaka 
> >> wrote:
> >>
> >>> Hi Brahma,
> >>>
> >>> Thank you for preparing the release.
> >>> Could you cut branch-3.3.0? I would like to backport some fixes for
> >>> 3.3.1 and not for 3.3.0.
> >>>
> >>> Thanks and regards,
> >>> Akira
> >>>
> >>> On Fri, Apr 17, 2020 at 11:11 AM Brahma Reddy Battula <
> bra...@apache.org>
> >>> wrote:
> >>>
>  Hi All,
> 
>  we are down to two blockers issues now (YARN-10194 and YARN-9848)
> which
>  are in patch available state.Hopefully we can out the RC soon.
> 
>  thanks to @Prabhu Joseph 
> ,@masakate,@akira
>  and @Wei-Chiu Chuang   and others for helping
>  resloving the blockers.
> 
> 
> 
>  On Tue, Apr 14, 2020 at 10:49 PM Brahma Reddy Battula <
>  bra...@apache.org> wrote:
> 
> >
> > @Prabhu Joseph 
> > >>> Have committed the YARN blocker YARN-10219 to trunk and
> > cherry-picked to branch-3.3. Right now, there are two blocker Jiras -
> > YARN-10233 and HADOOP-16982
> > which i will help to review and commit. Thanks.
> >
> > Looks you committed YARN-10219. Noted YARN-10233 and HADOOP-16982 as
> a
> > blockers. (without YARN-10233 we have given so many releases,it's
> not newly
> > introduced.).. Thanks
> >
> > @Vinod Kumar Vavilapalli  ,@adam Antal,
> >
> > I noted YARN-9848 as a blocker as you mentioned above.
> >
> > @All,
> >
> > Currently following four blockers are pending for 3.3.0 RC.
> >
> > HADOOP-16963,YARN-10233,HADOOP-16982 and YARN-9848.
> >
> >
> >
> > On Tue, Apr 14, 2020 at 8:11 PM Vinod Kumar Vavilapalli <
> > vino...@apache.org> wrote:
> >
> >> Looks like a really bad bug to me.
> >>
> >> +1 for revert and +1 for making that a 3.3.0 blocker. I think should
> >> also revert it in a 3.2 maintenance release too.
> >>
> >> Thanks
> >> +Vinod
> >>
> >> > On Apr 14, 2020, at 5:03 PM, Adam Antal  .INVALID>
> >> wrote:
> >> >
> >> > Hi everyone,
> >> >
> >> > Sorry for coming a bit late with this, but there's also one jira
> >> that can
> >> > have potential impact on clusters and we should talk about it.
> >> >
> >> > Steven Rand found this problem earlier and commented to
> >> > https://issues.apache.org/jira/browse/YARN-4946.
> >> > The bug has impact on the RM state store: the RM does not delete
> >> apps - see
> >> > more details in his comment here:
> >> >
> >>
> https://issues.apache.org/jira/browse/YARN-4946?focusedCommentId=16898599=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16898599
> >> > .
> >> > (FYI He also created
> >> https://issues.apache.org/jira/browse/YARN-9848 with
> >> > the revert task).
> >> >
> >> > It might not be an actual blocker, but since there wasn't any
> >> consensus
> >> > about a follow up action, I thought we should decide how to
> proceed
> >> before
> >> > release 3.3.0.
> >> >
> >> > Regards,
> >> > Adam
> >> >
> >> > On Tue, Apr 14, 2020 at 9:35 AM Prabhu Joseph <
> >> prabhujose.ga...@gmail.com>
> >> > wrote:
> >> >
> >> >> Thanks Brahma for the update.
> >> >>
> >> >> Have committed the YARN blocker YARN-10219 to trunk and
> >> cherry-picked to
> >> >> branch-3.3. Right now, there are two blocker Jiras - YARN-10233
> and
> >> >> HADOOP-16982
> >> >> which i will help to review and commit. Thanks.
> >> >>
> >> >> [image: Screen Shot 2020-04-14 at 1.01.51 PM.png]
> >> >>
> >> >> project in (YARN, HADOOP, MAPREDUCE, HDFS) 

[jira] [Created] (HADOOP-17012) Remove Ratis dependencies from Hadoop branch-3.2

[Wei-Chiu Chuang (Jira)]

Wei-Chiu Chuang created HADOOP-17012:


 Summary: Remove Ratis dependencies from Hadoop branch-3.2
 Key: HADOOP-17012
 URL: https://issues.apache.org/jira/browse/HADOOP-17012
 Project: Hadoop Common
  Issue Type: Task
Affects Versions: 3.2.2
Reporter: Wei-Chiu Chuang


These are not used in the core Hadoop codebase. Remove them to avoid confusion.

{code}

0.3.0-eca3531-SNAPSHOT

  
org.apache.ratis
ratis-proto-shaded
${ratis.version}
  
  
ratis-common
org.apache.ratis
${ratis.version}
  
  
ratis-client
org.apache.ratis
${ratis.version}
  
  
ratis-server
org.apache.ratis
${ratis.version}
  
  
ratis-netty
org.apache.ratis
${ratis.version}
  
  
ratis-grpc
org.apache.ratis
${ratis.version}
  
{code}

These are removed from trunk already.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

Re: [Hadoop-3.3 Release update]- branch-3.3 has created

[Wei-Chiu Chuang]

+1 we should have the branch ASAP.

On Wed, Apr 22, 2020 at 11:07 PM Akira Ajisaka  wrote:

> > Since blockers are not closed, I didn't cut the branch because
> multiple branches might confuse or sombody might miss to commit.
>
> The current situation is already confusing. The 3.3.1 version already
> exists in JIRA, so some committers wrongly commit non-critical issues to
> branch-3.3 and set the fix version to 3.3.1.
> I think now we should cut branch-3.3.0 and freeze source code except the
> blockers.
>
> -Akira
>
> On Tue, Apr 21, 2020 at 3:05 PM Brahma Reddy Battula 
> wrote:
>
>> Sure, I will do that.
>>
>> Since blockers are not closed, I didn't cut the branch because
>> multiple branches might confuse or sombody might miss to commit.Shall I
>> wait till this weekend to create..?
>>
>> On Mon, Apr 20, 2020 at 11:57 AM Akira Ajisaka 
>> wrote:
>>
>>> Hi Brahma,
>>>
>>> Thank you for preparing the release.
>>> Could you cut branch-3.3.0? I would like to backport some fixes for
>>> 3.3.1 and not for 3.3.0.
>>>
>>> Thanks and regards,
>>> Akira
>>>
>>> On Fri, Apr 17, 2020 at 11:11 AM Brahma Reddy Battula 
>>> wrote:
>>>
 Hi All,

 we are down to two blockers issues now (YARN-10194 and YARN-9848) which
 are in patch available state.Hopefully we can out the RC soon.

 thanks to @Prabhu Joseph  ,@masakate,@akira
 and @Wei-Chiu Chuang   and others for helping
 resloving the blockers.



 On Tue, Apr 14, 2020 at 10:49 PM Brahma Reddy Battula <
 bra...@apache.org> wrote:

>
> @Prabhu Joseph 
> >>> Have committed the YARN blocker YARN-10219 to trunk and
> cherry-picked to branch-3.3. Right now, there are two blocker Jiras -
> YARN-10233 and HADOOP-16982
> which i will help to review and commit. Thanks.
>
> Looks you committed YARN-10219. Noted YARN-10233 and HADOOP-16982 as a
> blockers. (without YARN-10233 we have given so many releases,it's not 
> newly
> introduced.).. Thanks
>
> @Vinod Kumar Vavilapalli  ,@adam Antal,
>
> I noted YARN-9848 as a blocker as you mentioned above.
>
> @All,
>
> Currently following four blockers are pending for 3.3.0 RC.
>
> HADOOP-16963,YARN-10233,HADOOP-16982 and YARN-9848.
>
>
>
> On Tue, Apr 14, 2020 at 8:11 PM Vinod Kumar Vavilapalli <
> vino...@apache.org> wrote:
>
>> Looks like a really bad bug to me.
>>
>> +1 for revert and +1 for making that a 3.3.0 blocker. I think should
>> also revert it in a 3.2 maintenance release too.
>>
>> Thanks
>> +Vinod
>>
>> > On Apr 14, 2020, at 5:03 PM, Adam Antal 
>> > 
>> wrote:
>> >
>> > Hi everyone,
>> >
>> > Sorry for coming a bit late with this, but there's also one jira
>> that can
>> > have potential impact on clusters and we should talk about it.
>> >
>> > Steven Rand found this problem earlier and commented to
>> > https://issues.apache.org/jira/browse/YARN-4946.
>> > The bug has impact on the RM state store: the RM does not delete
>> apps - see
>> > more details in his comment here:
>> >
>> https://issues.apache.org/jira/browse/YARN-4946?focusedCommentId=16898599=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16898599
>> > .
>> > (FYI He also created
>> https://issues.apache.org/jira/browse/YARN-9848 with
>> > the revert task).
>> >
>> > It might not be an actual blocker, but since there wasn't any
>> consensus
>> > about a follow up action, I thought we should decide how to proceed
>> before
>> > release 3.3.0.
>> >
>> > Regards,
>> > Adam
>> >
>> > On Tue, Apr 14, 2020 at 9:35 AM Prabhu Joseph <
>> prabhujose.ga...@gmail.com>
>> > wrote:
>> >
>> >> Thanks Brahma for the update.
>> >>
>> >> Have committed the YARN blocker YARN-10219 to trunk and
>> cherry-picked to
>> >> branch-3.3. Right now, there are two blocker Jiras - YARN-10233 and
>> >> HADOOP-16982
>> >> which i will help to review and commit. Thanks.
>> >>
>> >> [image: Screen Shot 2020-04-14 at 1.01.51 PM.png]
>> >>
>> >> project in (YARN, HADOOP, MAPREDUCE, HDFS) AND priority in
>> (Blocker,
>> >> Critical) AND resolution = Unresolved AND "Target Version/s" =
>> 3.3.0 ORDER
>> >> BY priority DESC
>> >>
>> >>
>> >> On Sun, Apr 12, 2020 at 12:19 AM Brahma Reddy Battula <
>> bra...@apache.org>
>> >> wrote:
>> >>
>> >>> *Pending for 3.3.0 Release:*
>> >>>
>> >>> One Blocker(HADOOP-16963) confirmation and following jira's are
>> open as
>> >>> these needs to merged to other branches(I am tracking the same,
>> Ideally
>> >>> this can be closed and can raise seperate jira's to track).
>> >>>
>> >>>
>> >>> 1–4 of 4Refresh results
>> >>> <
>> >>>
>> 

Apache Hadoop qbt Report: branch2.10+JDK7 on Linux/x86

[Apache Jenkins Server]

For more details, see 
https://builds.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86/665/

No changes




-1 overall


The following subsystems voted -1:
asflicense findbugs hadolint pathlen unit xml


The following subsystems voted -1 but
were configured to be filtered/ignored:
cc checkstyle javac javadoc pylint shellcheck shelldocs whitespace


The following subsystems are considered long running:
(runtime bigger than 1h  0m  0s)
unit


Specific tests:

XML :

   Parsing Error(s): 
   
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/conf/empty-configuration.xml
 
   hadoop-tools/hadoop-azure/src/config/checkstyle-suppressions.xml 
   hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/public/crossdomain.xml 
   
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp/public/crossdomain.xml
 

FindBugs :

   module:hadoop-common-project/hadoop-minikdc 
   Possible null pointer dereference in 
org.apache.hadoop.minikdc.MiniKdc.delete(File) due to return value of called 
method Dereferenced at 
MiniKdc.java:org.apache.hadoop.minikdc.MiniKdc.delete(File) due to return value 
of called method Dereferenced at MiniKdc.java:[line 515] 

FindBugs :

   module:hadoop-common-project/hadoop-auth 
   
org.apache.hadoop.security.authentication.server.MultiSchemeAuthenticationHandler.authenticate(HttpServletRequest,
 HttpServletResponse) makes inefficient use of keySet iterator instead of 
entrySet iterator At MultiSchemeAuthenticationHandler.java:of keySet iterator 
instead of entrySet iterator At MultiSchemeAuthenticationHandler.java:[line 
192] 

FindBugs :

   module:hadoop-common-project/hadoop-common 
   org.apache.hadoop.crypto.CipherSuite.setUnknownValue(int) 
unconditionally sets the field unknownValue At CipherSuite.java:unknownValue At 
CipherSuite.java:[line 44] 
   org.apache.hadoop.crypto.CryptoProtocolVersion.setUnknownValue(int) 
unconditionally sets the field unknownValue At 
CryptoProtocolVersion.java:unknownValue At CryptoProtocolVersion.java:[line 67] 
   Possible null pointer dereference in 
org.apache.hadoop.fs.FileUtil.fullyDeleteOnExit(File) due to return value of 
called method Dereferenced at 
FileUtil.java:org.apache.hadoop.fs.FileUtil.fullyDeleteOnExit(File) due to 
return value of called method Dereferenced at FileUtil.java:[line 118] 
   Possible null pointer dereference in 
org.apache.hadoop.fs.RawLocalFileSystem.handleEmptyDstDirectoryOnWindows(Path, 
File, Path, File) due to return value of called method Dereferenced at 
RawLocalFileSystem.java:org.apache.hadoop.fs.RawLocalFileSystem.handleEmptyDstDirectoryOnWindows(Path,
 File, Path, File) due to return value of called method Dereferenced at 
RawLocalFileSystem.java:[line 383] 
   Useless condition:lazyPersist == true at this point At 
CommandWithDestination.java:[line 502] 
   org.apache.hadoop.io.DoubleWritable.compareTo(DoubleWritable) 
incorrectly handles double value At DoubleWritable.java: At 
DoubleWritable.java:[line 78] 
   org.apache.hadoop.io.DoubleWritable$Comparator.compare(byte[], int, int, 
byte[], int, int) incorrectly handles double value At DoubleWritable.java:int) 
incorrectly handles double value At DoubleWritable.java:[line 97] 
   org.apache.hadoop.io.FloatWritable.compareTo(FloatWritable) incorrectly 
handles float value At FloatWritable.java: At FloatWritable.java:[line 71] 
   org.apache.hadoop.io.FloatWritable$Comparator.compare(byte[], int, int, 
byte[], int, int) incorrectly handles float value At FloatWritable.java:int) 
incorrectly handles float value At FloatWritable.java:[line 89] 
   Possible null pointer dereference in 
org.apache.hadoop.io.IOUtils.listDirectory(File, FilenameFilter) due to return 
value of called method Dereferenced at 
IOUtils.java:org.apache.hadoop.io.IOUtils.listDirectory(File, FilenameFilter) 
due to return value of called method Dereferenced at IOUtils.java:[line 389] 
   Possible bad parsing of shift operation in 
org.apache.hadoop.io.file.tfile.Utils$Version.hashCode() At 
Utils.java:operation in 
org.apache.hadoop.io.file.tfile.Utils$Version.hashCode() At Utils.java:[line 
398] 
   
org.apache.hadoop.metrics2.lib.DefaultMetricsFactory.setInstance(MutableMetricsFactory)
 unconditionally sets the field mmfImpl At DefaultMetricsFactory.java:mmfImpl 
At DefaultMetricsFactory.java:[line 49] 
   
org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.setMiniClusterMode(boolean) 
unconditionally sets the field miniClusterMode At 
DefaultMetricsSystem.java:miniClusterMode At DefaultMetricsSystem.java:[line 
92] 
   Useless object stored in variable seqOs of method 
org.apache.hadoop.security.token.delegation.ZKDelegationTokenSecretManager.addOrUpdateToken(AbstractDelegationTokenIdentifier,
 AbstractDelegationTokenSecretManager$DelegationTokenInformation, boolean) At 
ZKDelegationTokenSecretManager.java:seqOs of method 

[jira] [Resolved] (HADOOP-16193) add extra S3A MPU test to see what happens if a file is created during the MPU

[Steve Loughran (Jira)]

 [ 
https://issues.apache.org/jira/browse/HADOOP-16193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Loughran resolved HADOOP-16193.
-
Resolution: Won't Fix

> add extra S3A MPU test to see what happens if a file is created during the MPU
> --
>
> Key: HADOOP-16193
> URL: https://issues.apache.org/jira/browse/HADOOP-16193
> Project: Hadoop Common
>  Issue Type: Sub-task
>  Components: fs/s3
>Reporter: Steve Loughran
>Assignee: Steve Loughran
>Priority: Minor
> Fix For: 3.1.5
>
>
> Proposed extra test for the S3A MPU: if you create and then delete a file 
> while an MPU is in progress, when you finally complete the MPU the new data 
> is present.
> This verifies that the other FS operations don't somehow cancel the 
> in-progress upload, and that eventual consistency brings the latest value out.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org