[jira] [Created] (HADOOP-19148) Update solr from 8.11.2 to 8.11.3 to address CVE-2023-50298
Brahma Reddy Battula created HADOOP-19148: - Summary: Update solr from 8.11.2 to 8.11.3 to address CVE-2023-50298 Key: HADOOP-19148 URL: https://issues.apache.org/jira/browse/HADOOP-19148 Project: Hadoop Common Issue Type: Improvement Components: common Reporter: Brahma Reddy Battula Update solr from 8.11.2 to 8.11.3 to address CVE-2023-50298 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-16795) Java 11 compile support
[ https://issues.apache.org/jira/browse/HADOOP-16795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816376#comment-17816376 ] Brahma Reddy Battula commented on HADOOP-16795: --- Hi [~vinay._.devadiga] and [~DavinC] There is jdk17 Jira (HADOOP-17177 ) , Please feel free to assign any jira's. > Java 11 compile support > --- > > Key: HADOOP-16795 > URL: https://issues.apache.org/jira/browse/HADOOP-16795 > Project: Hadoop Common > Issue Type: Improvement > Components: build >Reporter: Akira Ajisaka >Priority: Major > > Split from HADOOP-15338. > Now Hadoop must be compiled with Java 8. This issue is to support compiling > Hadoop with Java 11. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-19070) Java 17 compile support
[
https://issues.apache.org/jira/browse/HADOOP-19070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816375#comment-17816375
]
Brahma Reddy Battula commented on HADOOP-19070:
---
[~slfan1989] thanks for reporting this and working on this. I just linked to
the parent Jira as [~bteke] mentioned.
{quote}maybe in the 3.4.0 release we should warn "this is java8 compatible but
support may soon be dropped with java11 the baseline"
{quote}
Sure, we can try to do that.
> Java 17 compile support
> ---
>
> Key: HADOOP-19070
> URL: https://issues.apache.org/jira/browse/HADOOP-19070
> Project: Hadoop Common
> Issue Type: Task
>Reporter: Shilun Fan
>Priority: Major
>
> We plan to make Hadoop compatible with Java 17. There is a lot of work to be
> done, but we still aim to complete this task by 2024.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-18953) Java 17 runtime library upgrade prerequisites
[ https://issues.apache.org/jira/browse/HADOOP-18953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17816370#comment-17816370 ] Brahma Reddy Battula commented on HADOOP-18953: --- [~pulparindo] thanks for reporting this. Are you plan to work on this. > Java 17 runtime library upgrade prerequisites > - > > Key: HADOOP-18953 > URL: https://issues.apache.org/jira/browse/HADOOP-18953 > Project: Hadoop Common > Issue Type: Improvement > Components: build >Reporter: Bruno Ramirez >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17225) Update jackson-mapper-asl-1.9.13 to atlassian version to mitigate: CVE-2019-10172
[ https://issues.apache.org/jira/browse/HADOOP-17225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17771336#comment-17771336 ] Brahma Reddy Battula commented on HADOOP-17225: --- thanks [~fanningpj] . Does 3.3 has the compatibility with 3.2 (example: hadoop-3.2 client can connect with hadoop-3.3 server)..? Bytheway I didn't follow up the changes. > Update jackson-mapper-asl-1.9.13 to atlassian version to mitigate: > CVE-2019-10172 > - > > Key: HADOOP-17225 > URL: https://issues.apache.org/jira/browse/HADOOP-17225 > Project: Hadoop Common > Issue Type: Bug >Reporter: Brahma Reddy Battula >Assignee: Brahma Reddy Battula >Priority: Major > Attachments: HADOOP-17225-001.patch, HADOOP-17225-002.patch > > > Currently jersey depends on the jackson, and upgradation of jersey from 1.X > to 2.x looks complicated(see HADOOP-15984 and HADOOP-16485). > Update jackson-mapper-asl-1.9.13 to atlassian version to mitigate: > CVE-2019-10172. > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-18581) Handle Server KDC re-login when Server and Client run in same JVM.
[
https://issues.apache.org/jira/browse/HADOOP-18581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17655832#comment-17655832
]
Brahma Reddy Battula commented on HADOOP-18581:
---
[~surendralilhore] thanks for reporting and working on this. Are you planning
to backport to other branches also..?
{quote}When JN client try to re-login and it fails, it will destroy server
service ticket also and NameNode not able to server client request. We can see
the below error logs in NameNode log file.
{quote}
Any insights on when this can happen.. I checked your testcase which logout on
other thread, but will be case..?
Are you using kerboes-1.15 client or kerboes-1.13 client.?
> Handle Server KDC re-login when Server and Client run in same JVM.
> --
>
> Key: HADOOP-18581
> URL: https://issues.apache.org/jira/browse/HADOOP-18581
> Project: Hadoop Common
> Issue Type: Bug
>Affects Versions: 3.1.1
>Reporter: Surendra Singh Lilhore
>Assignee: Surendra Singh Lilhore
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0
>
>
> Handle re-login in Server when client, server running in same JVM and client
> trying to re-login, but it fails.
> For example, NameNode is server but in same JVM journal node client also
> running to push to edit logs. When JN client try to re-login and it fails, it
> will destroy server service ticket also and NameNode not able to server
> client request. We can see the below error logs in NameNode log file.
>
> {noformat}
> Auth failed for x.x.x.x:42199:null (GSS initiate failed) with true cause:
> (GSS initiate failed)
> Auth failed for x.x.x.x:42199:null (GSS initiate failed) with true cause:
> (GSS initiate failed)
> Auth failed for x.x.x.x:42199:null (GSS initiate failed) with true cause:
> (GSS initiate failed){noformat}
> Same discussion happened in HADOOP-17996.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-18342) Upgrade to Avro 1.11.1
[ https://issues.apache.org/jira/browse/HADOOP-18342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652051#comment-17652051 ] Brahma Reddy Battula commented on HADOOP-18342: --- Looks third party PR is merged,Still this is valid ? > Upgrade to Avro 1.11.1 > -- > > Key: HADOOP-18342 > URL: https://issues.apache.org/jira/browse/HADOOP-18342 > Project: Hadoop Common > Issue Type: Improvement >Reporter: PJ Fanning >Priority: Major > Labels: pull-request-available > Time Spent: 3.5h > Remaining Estimate: 0h > > Latest version of Avro. Aimed only at trunk as there is no security concern > addressed here. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-18538) Upgrade kafka to 2.8.2
[ https://issues.apache.org/jira/browse/HADOOP-18538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated HADOOP-18538: -- Fix Version/s: 3.4.0 Resolution: Fixed Status: Resolved (was: Patch Available) Closing this as it's already merged to trunk. Good to have other branches. > Upgrade kafka to 2.8.2 > -- > > Key: HADOOP-18538 > URL: https://issues.apache.org/jira/browse/HADOOP-18538 > Project: Hadoop Common > Issue Type: Improvement > Components: build >Affects Versions: 3.4.0 >Reporter: D M Murali Krishna Reddy >Assignee: D M Murali Krishna Reddy >Priority: Major > Labels: pull-request-available > Fix For: 3.4.0 > > > Upgrade kafka to 2.8.2 to resolve > [CVE-2022-34917|https://nvd.nist.gov/vuln/detail/CVE-2022-34917] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (HADOOP-18566) Set Cache-Control no-store max-age as 0 header on all dynamic content
[ https://issues.apache.org/jira/browse/HADOOP-18566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645577#comment-17645577 ] Brahma Reddy Battula edited comment on HADOOP-18566 at 12/10/22 10:52 AM: -- Currently we are setting only "no-cache" no-cache filter. There should be probability of session hijack. As browsers to store pages under the user's browser cache. On a public computer, a shared system or a machine in a semi-public area such as a call center, a malicious person may search through the browser cache to locate the sensitive information cached during the previous user's session was (Author: brahmareddy): I think, it's good to have as per security concern. > Set Cache-Control no-store max-age as 0 header on all dynamic content > - > > Key: HADOOP-18566 > URL: https://issues.apache.org/jira/browse/HADOOP-18566 > Project: Hadoop Common > Issue Type: Bug >Reporter: Bilwa S T >Assignee: Bilwa S T >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-18566) Set Cache-Control no-store max-age as 0 header on all dynamic content
[ https://issues.apache.org/jira/browse/HADOOP-18566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17645577#comment-17645577 ] Brahma Reddy Battula commented on HADOOP-18566: --- I think, it's good to have as per security concern. > Set Cache-Control no-store max-age as 0 header on all dynamic content > - > > Key: HADOOP-18566 > URL: https://issues.apache.org/jira/browse/HADOOP-18566 > Project: Hadoop Common > Issue Type: Bug >Reporter: Bilwa S T >Assignee: Bilwa S T >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-18538) Upgrade kafka to 2.8.2
[ https://issues.apache.org/jira/browse/HADOOP-18538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643962#comment-17643962 ] Brahma Reddy Battula commented on HADOOP-18538: --- [~dmmkr] thanks for reporting. Committed to trunk. > Upgrade kafka to 2.8.2 > -- > > Key: HADOOP-18538 > URL: https://issues.apache.org/jira/browse/HADOOP-18538 > Project: Hadoop Common > Issue Type: Improvement > Components: build >Affects Versions: 3.4.0 >Reporter: D M Murali Krishna Reddy >Assignee: D M Murali Krishna Reddy >Priority: Major > Labels: pull-request-available > > Upgrade kafka to 2.8.2 to resolve > [CVE-2022-34917|https://nvd.nist.gov/vuln/detail/CVE-2022-34917] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-18538) Upgrade kafka to 2.8.2
[ https://issues.apache.org/jira/browse/HADOOP-18538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated HADOOP-18538: -- Status: Patch Available (was: Open) > Upgrade kafka to 2.8.2 > -- > > Key: HADOOP-18538 > URL: https://issues.apache.org/jira/browse/HADOOP-18538 > Project: Hadoop Common > Issue Type: Improvement > Components: build >Affects Versions: 3.4.0 >Reporter: D M Murali Krishna Reddy >Assignee: D M Murali Krishna Reddy >Priority: Major > Labels: pull-request-available > > Upgrade kafka to 2.8.2 to resolve > [CVE-2022-34917|https://nvd.nist.gov/vuln/detail/CVE-2022-34917] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-18550) Web UI has no session controller.There is a risk of session hijacking.
[ https://issues.apache.org/jira/browse/HADOOP-18550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643630#comment-17643630 ] Brahma Reddy Battula commented on HADOOP-18550: --- [~rickboker] thanks for reporting, Are you planning to work on this.? > Web UI has no session controller.There is a risk of session hijacking. > -- > > Key: HADOOP-18550 > URL: https://issues.apache.org/jira/browse/HADOOP-18550 > Project: Hadoop Common > Issue Type: Improvement > Components: website >Affects Versions: 3.3.1 >Reporter: rickboker >Priority: Major > > When I browse the webui,and keep this page connect. the session which jetty > given me.And session will keep alive as long as page alive. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-18443) Upgrade snakeyaml to 1.31 to mitigate CVE-2022-25857
[ https://issues.apache.org/jira/browse/HADOOP-18443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601852#comment-17601852 ] Brahma Reddy Battula commented on HADOOP-18443: --- [~groot] thanks for your contribution . Committed to trunk. are you plan provide PR for lower branches also..? > Upgrade snakeyaml to 1.31 to mitigate CVE-2022-25857 > > > Key: HADOOP-18443 > URL: https://issues.apache.org/jira/browse/HADOOP-18443 > Project: Hadoop Common > Issue Type: Bug > Components: security >Affects Versions: 3.3.3, 3.3.4 >Reporter: groot >Assignee: groot >Priority: Major > Labels: pull-request-available > > Upgrade snakeyaml to 1.31 to mitigate CVE-2022-25857 > > Details - https://nvd.nist.gov/vuln/detail/CVE-2022-25857 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-18443) Upgrade snakeyaml to 1.31 to mitigate CVE-2022-25857
[ https://issues.apache.org/jira/browse/HADOOP-18443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated HADOOP-18443: -- Status: Patch Available (was: Open) > Upgrade snakeyaml to 1.31 to mitigate CVE-2022-25857 > > > Key: HADOOP-18443 > URL: https://issues.apache.org/jira/browse/HADOOP-18443 > Project: Hadoop Common > Issue Type: Bug > Components: security >Affects Versions: 3.3.4, 3.3.3 >Reporter: groot >Assignee: groot >Priority: Major > Labels: pull-request-available > > Upgrade snakeyaml to 1.31 to mitigate CVE-2022-25857 > > Details - https://nvd.nist.gov/vuln/detail/CVE-2022-25857 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-18311) Upgrade dependencies to address several CVEs
[ https://issues.apache.org/jira/browse/HADOOP-18311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17557896#comment-17557896 ] Brahma Reddy Battula commented on HADOOP-18311: --- [~svaughan] can this be plan to branch-3.2 also..? > Upgrade dependencies to address several CVEs > > > Key: HADOOP-18311 > URL: https://issues.apache.org/jira/browse/HADOOP-18311 > Project: Hadoop Common > Issue Type: Improvement > Components: common >Affects Versions: 3.3.3, 3.3.4 >Reporter: Steve Vaughan >Priority: Major > Labels: pull-request-available > Fix For: 3.3.4 > > Time Spent: 50m > Remaining Estimate: 0h > > The following CVEs can be addressed by upgrading dependencies within the > build. This includes a replacement of HTrace with a noop implementation. > * CVE-2018-7489 > * CVE-2020-10663 > * CVE-2020-28491 > * CVE-2020-35490 > * CVE-2020-35491 > * CVE-2020-36518 > * PRISMA-2021-0182 > This addresses all of the CVEs from 3.3.3 except for ones that would require > upgrading Netty to 4.x. I'll be submitting a pull request for 3.3.4. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-18088) Replace log4j 1.x with reload4j
[ https://issues.apache.org/jira/browse/HADOOP-18088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17522387#comment-17522387 ] Brahma Reddy Battula commented on HADOOP-18088: --- Looks this is re-opened,does this breaks I didn't found the any comment on re-open.? > Replace log4j 1.x with reload4j > --- > > Key: HADOOP-18088 > URL: https://issues.apache.org/jira/browse/HADOOP-18088 > Project: Hadoop Common > Issue Type: Improvement >Reporter: Wei-Chiu Chuang >Assignee: Wei-Chiu Chuang >Priority: Major > Labels: pull-request-available > Fix For: 2.10.2, 3.2.4, 3.3.4 > > Time Spent: 7.5h > Remaining Estimate: 0h > > As proposed in the dev mailing list > (https://lists.apache.org/thread/fdzkv80mzkf3w74z9120l0k0rc3v7kqk) let's > replace log4j 1 with reload4j in the maintenance releases (i.e. 3.3.x, 3.2.x > and 2.10.x) -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-13500) Synchronizing iteration of Configuration properties object
[ https://issues.apache.org/jira/browse/HADOOP-13500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461558#comment-17461558 ] Brahma Reddy Battula commented on HADOOP-13500: --- [~aajisaka] will you cherry-pick to branch-3.2.3 also..? Or shall I do..? > Synchronizing iteration of Configuration properties object > -- > > Key: HADOOP-13500 > URL: https://issues.apache.org/jira/browse/HADOOP-13500 > Project: Hadoop Common > Issue Type: Bug > Components: conf >Reporter: Jason Darrell Lowe >Assignee: Dhananjay Badaya >Priority: Major > Labels: pull-request-available > Fix For: 3.4.0, 2.10.2, 3.2.4, 3.3.3 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > It is possible to encounter a ConcurrentModificationException while trying to > iterate a Configuration object. The iterator method tries to walk the > underlying Property object without proper synchronization, so another thread > simultaneously calling the set method can trigger it. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-16905) Update jackson-databind to 2.10.3 to relieve us from the endless CVE patches
[ https://issues.apache.org/jira/browse/HADOOP-16905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated HADOOP-16905: -- Fix Version/s: 3.2.3 > Update jackson-databind to 2.10.3 to relieve us from the endless CVE patches > > > Key: HADOOP-16905 > URL: https://issues.apache.org/jira/browse/HADOOP-16905 > Project: Hadoop Common > Issue Type: Sub-task >Reporter: Wei-Chiu Chuang >Assignee: Wei-Chiu Chuang >Priority: Major > Labels: pull-request-available, release-blocker > Fix For: 3.3.0, 3.2.3, 3.2.4 > > Time Spent: 5h 10m > Remaining Estimate: 0h > > Jackson-databind 2.10 should relieve us from the endless CVE patches > according to > https://medium.com/@cowtowncoder/jackson-2-10-features-cd880674d8a2 > Not sure if this is an easy update, but i think we should do this in the > Hadoop 3.3.0 and before removing jackson-databind entirely. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-16905) Update jackson-databind to 2.10.3 to relieve us from the endless CVE patches
[ https://issues.apache.org/jira/browse/HADOOP-16905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460810#comment-17460810 ] Brahma Reddy Battula commented on HADOOP-16905: --- Committed to branch-3.2.3.. Thanks all. > Update jackson-databind to 2.10.3 to relieve us from the endless CVE patches > > > Key: HADOOP-16905 > URL: https://issues.apache.org/jira/browse/HADOOP-16905 > Project: Hadoop Common > Issue Type: Sub-task >Reporter: Wei-Chiu Chuang >Assignee: Wei-Chiu Chuang >Priority: Major > Labels: pull-request-available, release-blocker > Fix For: 3.3.0, 3.2.4 > > Time Spent: 5h 10m > Remaining Estimate: 0h > > Jackson-databind 2.10 should relieve us from the endless CVE patches > according to > https://medium.com/@cowtowncoder/jackson-2-10-features-cd880674d8a2 > Not sure if this is an easy update, but i think we should do this in the > Hadoop 3.3.0 and before removing jackson-databind entirely. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-18037) Backport HADOOP-17796 for branch-3.2
[ https://issues.apache.org/jira/browse/HADOOP-18037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17455328#comment-17455328 ] Brahma Reddy Battula commented on HADOOP-18037: --- [~ananysin] thanks for working on this, as this only pom changes, testcases will not executed.. can you some dummy changes with this patch so that UT will be executed..? > Backport HADOOP-17796 for branch-3.2 > > > Key: HADOOP-18037 > URL: https://issues.apache.org/jira/browse/HADOOP-18037 > Project: Hadoop Common > Issue Type: Bug >Affects Versions: 3.2.2 >Reporter: Ananya Singh >Assignee: Ananya Singh >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-15685) Build fails (hadoop pipes) on newer Linux envs (like Fedora 28)
[ https://issues.apache.org/jira/browse/HADOOP-15685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17446267#comment-17446267 ] Brahma Reddy Battula commented on HADOOP-15685: --- [~iwasakims] did you get chance run on RHEL 8 also..? > Build fails (hadoop pipes) on newer Linux envs (like Fedora 28) > --- > > Key: HADOOP-15685 > URL: https://issues.apache.org/jira/browse/HADOOP-15685 > Project: Hadoop Common > Issue Type: Improvement > Components: build, tools/pipes >Affects Versions: 3.2.0 >Reporter: Lars Hofhansl >Assignee: Lars Hofhansl >Priority: Major > Attachments: 15685-3.2.0.txt, 15685-example.txt, > HADOOP-15685.001.patch > > > The rpc/types.h and similar includes are no longer part of glibc. > Instead tirpc needs to be used now on those systems. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17996) UserGroupInformation#unprotectedRelogin sets the last login time before logging in
[
https://issues.apache.org/jira/browse/HADOOP-17996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443809#comment-17443809
]
Brahma Reddy Battula commented on HADOOP-17996:
---
[~prabhujoseph] and [~Sushma_28]
thanks for reporting and working on this..IMO, this was just to track the
re-login attempt so that so many retries can be avoided.?
Configuring *kerberosMinSecondsBeforeRelogin* with low value will not work here
if it's needed.?
After this fix , on failure it will continuously retry..?
> UserGroupInformation#unprotectedRelogin sets the last login time before
> logging in
> --
>
> Key: HADOOP-17996
> URL: https://issues.apache.org/jira/browse/HADOOP-17996
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
>Affects Versions: 3.3.1
>Reporter: Prabhu Joseph
>Assignee: Ravuri Sushma sree
>Priority: Major
> Attachments: HADOOP-17996.001.patch
>
>
> UserGroupInformation#unprotectedRelogin sets the last login time before
> logging in. IPC#Client does reloginFromKeytab when there is a connection
> reset failure from AD which does logout and set the last login time to now
> and then tries to login. The login also fails as not able to connect to AD.
> Then the reattempts does not happen as kerberosMinSecondsBeforeRelogin check
> fails. All Client and Server operations fails with *GSS initiate failed*
> {code}
> 2021-10-31 09:50:53,546 WARN ha.EditLogTailer - Unable to trigger a roll of
> the active NN
> java.util.concurrent.ExecutionException:
> org.apache.hadoop.security.KerberosAuthException: DestHost:destPort
> namenode0:8020 , LocalHost:localPort namenode1/1.2.3.4:0. Failed on local
> exception: org.apache.hadoop.security.KerberosAuthException: Login failure
> for user: nn/nameno...@example.com javax.security.auth.login.LoginException:
> Connection reset
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:206)
> at
> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer.triggerActiveLogRoll(EditLogTailer.java:382)
> at
> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer$EditLogTailerThread.doWork(EditLogTailer.java:441)
> at
> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer$EditLogTailerThread.access$400(EditLogTailer.java:410)
> at
> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer$EditLogTailerThread$1.run(EditLogTailer.java:427)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:360)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1712)
> at
> org.apache.hadoop.security.SecurityUtil.doAsLoginUserOrFatal(SecurityUtil.java:480)
> at
> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer$EditLogTailerThread.run(EditLogTailer.java:423)
> Caused by: org.apache.hadoop.security.KerberosAuthException:
> DestHost:destPort namenode0:8020 , LocalHost:localPort namenode1/1.2.3.4:0.
> Failed on local exception: org.apache.hadoop.security.KerberosAuthException:
> Login failure for user: nn/nameno...@example.com
> javax.security.auth.login.LoginException: Connection reset
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at org.apache.hadoop.net.NetUtils.wrapWithMessage(NetUtils.java:831)
> at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:806)
> at org.apache.hadoop.ipc.Client.getRpcResponse(Client.java:1501)
> at org.apache.hadoop.ipc.Client.call(Client.java:1443)
> at org.apache.hadoop.ipc.Client.call(Client.java:1353)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:228)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:116)
> at com.sun.proxy.$Proxy21.rollEditLog(Unknown Source)
> at
> org.apache.hadoop.hdfs.protocolPB.NamenodeProtocolTranslatorPB.rollEditLog(NamenodeProtocolTranslatorPB.java:150)
> at
> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer$2.doWork(EditLogTailer.java:367)
> at
> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer$2.doWork(EditLogTailer.java:364)
> at
> org.apache.hadoop.hdfs.server.namenode.ha.EditLogTailer$MultipleNameNodeProxy.call(EditLogTailer.java:514)
> at
[jira] [Updated] (HADOOP-17972) Backport HADOOP-17683 for branch-3.2
[ https://issues.apache.org/jira/browse/HADOOP-17972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated HADOOP-17972: -- Status: Patch Available (was: Open) > Backport HADOOP-17683 for branch-3.2 > - > > Key: HADOOP-17972 > URL: https://issues.apache.org/jira/browse/HADOOP-17972 > Project: Hadoop Common > Issue Type: Bug > Components: security >Affects Versions: 3.2.2 >Reporter: Ananya Singh >Assignee: Ananya Singh >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > Our security tool raised the following security flaw on Hadoop 3.2.2: > CVE-2021-29425: [https://nvd.nist.gov/vuln/detail/CVE-2021-29425] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17972) Backport HADOOP-17683 for branch-3.2
[ https://issues.apache.org/jira/browse/HADOOP-17972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17430983#comment-17430983 ] Brahma Reddy Battula commented on HADOOP-17972: --- [~ananysin] thanks for reporting.. Added you to contributor list. Now you can assign this Jira yourself and upload the patch. Welcome to aboard!! Go through following for contribute guide. https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute > Backport HADOOP-17683 for branch-3.2 > - > > Key: HADOOP-17972 > URL: https://issues.apache.org/jira/browse/HADOOP-17972 > Project: Hadoop Common > Issue Type: Bug > Components: security >Affects Versions: 3.2.2 >Reporter: Ananya Singh >Priority: Major > > Our security tool raised the following security flaw on Hadoop 3.2.2: > CVE-2021-29425: [https://nvd.nist.gov/vuln/detail/CVE-2021-29425] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17014) Upgrade jackson-databind to 2.9.10.4
[ https://issues.apache.org/jira/browse/HADOOP-17014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17429822#comment-17429822 ] Brahma Reddy Battula commented on HADOOP-17014: --- [~smeng] and [~weichiu] , Can we consider HADOOP-16905 to branch-3.2 as I am planning to release the branch-3.2..? Even I commnented in the HADOOP-16905. > Upgrade jackson-databind to 2.9.10.4 > > > Key: HADOOP-17014 > URL: https://issues.apache.org/jira/browse/HADOOP-17014 > Project: Hadoop Common > Issue Type: Bug >Affects Versions: 3.1.4, 3.2.2 >Reporter: Siyao Meng >Assignee: Siyao Meng >Priority: Blocker > Fix For: 3.1.4, 3.2.2 > > > trunk (3.3.0) now has HADOOP-16905. But branch 3.2/3.1/.. still uses > jackson-databind 2.9. > I'm opening this jira since I'm unsure whether we are backporting > HADOOP-16905 to lower version branches due to compatibility concern or > whatever. > GH PR: https://github.com/apache/hadoop/pull/1981 > CC [~weichiu] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17683) Update commons-io to 2.8.0
[ https://issues.apache.org/jira/browse/HADOOP-17683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17429821#comment-17429821 ] Brahma Reddy Battula commented on HADOOP-17683: --- [~ananysin] aws changes are not straightforward, can you raise Jira to backport. > Update commons-io to 2.8.0 > -- > > Key: HADOOP-17683 > URL: https://issues.apache.org/jira/browse/HADOOP-17683 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Akira Ajisaka >Priority: Major > Labels: pull-request-available > Fix For: 3.3.1, 3.4.0 > > Time Spent: 40m > Remaining Estimate: 0h > > https://nvd.nist.gov/vuln/detail/CVE-2021-29425 > In Apache Commons IO before 2.7, When invoking the method > FileNameUtils.normalize with an improper input string, like "//../foo", or > "\\..\foo", the result would be the same value, thus possibly providing > access to files in the parent directory, but not further above (thus > "limited" path traversal), if the calling code would use the result to > construct a path value. > We don't use this API in the Hadoop code, but it's still good to update > anyway (we're on 2.5, which is 4 years old) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17236) Bump up snakeyaml to 1.26 to mitigate CVE-2017-18640
[ https://issues.apache.org/jira/browse/HADOOP-17236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17426136#comment-17426136 ] Brahma Reddy Battula commented on HADOOP-17236: --- Cherry-picked to branch-3.2 and branch-3.2.3. compiled and ran tests, didn't notice any failures.. [~ananysin] thanks to bringing me to my notice. > Bump up snakeyaml to 1.26 to mitigate CVE-2017-18640 > > > Key: HADOOP-17236 > URL: https://issues.apache.org/jira/browse/HADOOP-17236 > Project: Hadoop Common > Issue Type: Bug >Reporter: Brahma Reddy Battula >Assignee: Brahma Reddy Battula >Priority: Major > Fix For: 3.3.1, 3.4.0, 3.2.3 > > Attachments: HADOOP-17236-001-tempToRun.patch, HADOOP-17236-001.patch > > > Bump up snakeyaml to 1.26 to mitigate CVE-2017-18640 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17236) Bump up snakeyaml to 1.26 to mitigate CVE-2017-18640
[ https://issues.apache.org/jira/browse/HADOOP-17236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated HADOOP-17236: -- Fix Version/s: 3.2.3 > Bump up snakeyaml to 1.26 to mitigate CVE-2017-18640 > > > Key: HADOOP-17236 > URL: https://issues.apache.org/jira/browse/HADOOP-17236 > Project: Hadoop Common > Issue Type: Bug >Reporter: Brahma Reddy Battula >Assignee: Brahma Reddy Battula >Priority: Major > Fix For: 3.3.1, 3.4.0, 3.2.3 > > Attachments: HADOOP-17236-001-tempToRun.patch, HADOOP-17236-001.patch > > > Bump up snakeyaml to 1.26 to mitigate CVE-2017-18640 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17371) Bump Jetty to the latest version 9.4.35
[
https://issues.apache.org/jira/browse/HADOOP-17371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17425093#comment-17425093
]
Brahma Reddy Battula commented on HADOOP-17371:
---
{quote}Can we backport this to branch-3.2?
{quote}
Sure. [~weichiu] can we cherry-pick to branch-3.2..?
> Bump Jetty to the latest version 9.4.35
> ---
>
> Key: HADOOP-17371
> URL: https://issues.apache.org/jira/browse/HADOOP-17371
> Project: Hadoop Common
> Issue Type: Improvement
>Affects Versions: 3.3.1, 3.4.0, 3.2.3
>Reporter: Wei-Chiu Chuang
>Assignee: Wei-Chiu Chuang
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.3.1, 3.4.0
>
> Time Spent: 5h 10m
> Remaining Estimate: 0h
>
> The Hadoop 3 branches are on 9.4.20. We should update to the latest version:
> 9.4.34
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17834) Bump aliyun-sdk-oss to 3.13.0
[
https://issues.apache.org/jira/browse/HADOOP-17834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17425092#comment-17425092
]
Brahma Reddy Battula commented on HADOOP-17834:
---
{quote}Can we backport this to branch-3.2?
{quote}
Sure. [~aajisaka] please let me know your thought on this.
> Bump aliyun-sdk-oss to 3.13.0
> -
>
> Key: HADOOP-17834
> URL: https://issues.apache.org/jira/browse/HADOOP-17834
> Project: Hadoop Common
> Issue Type: Task
>Reporter: Siyao Meng
>Assignee: Siyao Meng
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0, 3.3.2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Bump aliyun-sdk-oss to 3.13.0 in order to remove transitive dependency on
> jdom 1.1.
> Ref:
> https://issues.apache.org/jira/browse/HADOOP-17820?focusedCommentId=17390206=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17390206.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17236) Bump up snakeyaml to 1.26 to mitigate CVE-2017-18640
[ https://issues.apache.org/jira/browse/HADOOP-17236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17425091#comment-17425091 ] Brahma Reddy Battula commented on HADOOP-17236: --- [~ananysin] Sure, thanks..will create Jira to cherry-pick this. > Bump up snakeyaml to 1.26 to mitigate CVE-2017-18640 > > > Key: HADOOP-17236 > URL: https://issues.apache.org/jira/browse/HADOOP-17236 > Project: Hadoop Common > Issue Type: Bug >Reporter: Brahma Reddy Battula >Assignee: Brahma Reddy Battula >Priority: Major > Fix For: 3.3.1, 3.4.0 > > Attachments: HADOOP-17236-001-tempToRun.patch, HADOOP-17236-001.patch > > > Bump up snakeyaml to 1.26 to mitigate CVE-2017-18640 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17254) Upgrade hbase to 1.4.13 on branch-2.10
[ https://issues.apache.org/jira/browse/HADOOP-17254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17425083#comment-17425083 ] Brahma Reddy Battula commented on HADOOP-17254: --- Thanks [~iwasakims] > Upgrade hbase to 1.4.13 on branch-2.10 > -- > > Key: HADOOP-17254 > URL: https://issues.apache.org/jira/browse/HADOOP-17254 > Project: Hadoop Common > Issue Type: Improvement >Reporter: Masatake Iwasaki >Assignee: Masatake Iwasaki >Priority: Major > Labels: pull-request-available > Fix For: 2.10.1 > > Time Spent: 50m > Remaining Estimate: 0h > > hbase.version must be updated to address CVE-2018-8025 on branch-2.10. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17254) Upgrade hbase to 1.4.13 on branch-2.10
[
https://issues.apache.org/jira/browse/HADOOP-17254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17424986#comment-17424986
]
Brahma Reddy Battula commented on HADOOP-17254:
---
{quote} I think we should cherry-pick YARN-8936 to branch-3.2 rather than this
(HADOOP-17254) if applicable.
{quote}
Yes
{quote}[~brahmareddy] Are you OK to push it to branch-3.2.3 too?
{quote}
Yes, Please.
> Upgrade hbase to 1.4.13 on branch-2.10
> --
>
> Key: HADOOP-17254
> URL: https://issues.apache.org/jira/browse/HADOOP-17254
> Project: Hadoop Common
> Issue Type: Improvement
>Reporter: Masatake Iwasaki
>Assignee: Masatake Iwasaki
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.10.1
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> hbase.version must be updated to address CVE-2018-8025 on branch-2.10.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17683) Update commons-io to 2.8.0
[ https://issues.apache.org/jira/browse/HADOOP-17683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17424877#comment-17424877 ] Brahma Reddy Battula commented on HADOOP-17683: --- [~aajisaka] this will be good candidate for 3.2.3 release, can we push it..? [~ananysin] thanks for bringing up this. > Update commons-io to 2.8.0 > -- > > Key: HADOOP-17683 > URL: https://issues.apache.org/jira/browse/HADOOP-17683 > Project: Hadoop Common > Issue Type: Task >Reporter: Wei-Chiu Chuang >Assignee: Akira Ajisaka >Priority: Major > Labels: pull-request-available > Fix For: 3.3.1, 3.4.0 > > Time Spent: 40m > Remaining Estimate: 0h > > https://nvd.nist.gov/vuln/detail/CVE-2021-29425 > In Apache Commons IO before 2.7, When invoking the method > FileNameUtils.normalize with an improper input string, like "//../foo", or > "\\..\foo", the result would be the same value, thus possibly providing > access to files in the parent directory, but not further above (thus > "limited" path traversal), if the calling code would use the result to > construct a path value. > We don't use this API in the Hadoop code, but it's still good to update > anyway (we're on 2.5, which is 4 years old) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-16905) Update jackson-databind to 2.10.3 to relieve us from the endless CVE patches
[ https://issues.apache.org/jira/browse/HADOOP-16905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17424874#comment-17424874 ] Brahma Reddy Battula commented on HADOOP-16905: --- [~weichiu] I think, we should backport this branch-3.2 so that this CVE will be fixed in upcoming release 3..2.3. > Update jackson-databind to 2.10.3 to relieve us from the endless CVE patches > > > Key: HADOOP-16905 > URL: https://issues.apache.org/jira/browse/HADOOP-16905 > Project: Hadoop Common > Issue Type: Sub-task >Reporter: Wei-Chiu Chuang >Assignee: Wei-Chiu Chuang >Priority: Major > Labels: pull-request-available, release-blocker > Fix For: 3.3.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Jackson-databind 2.10 should relieve us from the endless CVE patches > according to > https://medium.com/@cowtowncoder/jackson-2-10-features-cd880674d8a2 > Not sure if this is an easy update, but i think we should do this in the > Hadoop 3.3.0 and before removing jackson-databind entirely. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17221) update log4j-1.2.17 to atlassian version( To Address: CVE-2019-17571)
[ https://issues.apache.org/jira/browse/HADOOP-17221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17424841#comment-17424841 ] Brahma Reddy Battula commented on HADOOP-17221: --- [~kihwal] and [~aajisaka], let me know your thoughts on this issue. > update log4j-1.2.17 to atlassian version( To Address: CVE-2019-17571) > - > > Key: HADOOP-17221 > URL: https://issues.apache.org/jira/browse/HADOOP-17221 > Project: Hadoop Common > Issue Type: Bug >Reporter: Brahma Reddy Battula >Assignee: Brahma Reddy Battula >Priority: Major > Attachments: HADOOP-17221-001.patch, image-2020-08-25-07-39-09-201.png > > > Currentlly there are no active release under 1.X in log4j and log4j2 is > incompatiable to upgrade (see HADOOP-16206 ) for more details. > But following CVE is reported on log4j 1.2.17..I think,we should consider to > update to > Atlassian([https://mvnrepository.com/artifact/log4j/log4j/1.2.17-atlassian-0.4]) > or redhat versions > [https://nvd.nist.gov/vuln/detail/CVE-2019-17571] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17254) Upgrade hbase to 1.4.13 on branch-2.10
[
https://issues.apache.org/jira/browse/HADOOP-17254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17424839#comment-17424839
]
Brahma Reddy Battula commented on HADOOP-17254:
---
{quote}Ideally this should be applicable to branch-3.x. also. May I know why
this has been skipped for branch-3.x?
{quote}
Yes, we should backport to branch-3.2.. [~ananysin] thanks for pitching here.
{quote}YARN-8936 upgraded hbase.one.version from 1.2.6 to 1.4.8 and (on
branch-3.1 and above) without code change.
{quote}
[~iwasakims] it's not cherry-picked to branch-3.2 right..?
> Upgrade hbase to 1.4.13 on branch-2.10
> --
>
> Key: HADOOP-17254
> URL: https://issues.apache.org/jira/browse/HADOOP-17254
> Project: Hadoop Common
> Issue Type: Improvement
>Reporter: Masatake Iwasaki
>Assignee: Masatake Iwasaki
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.10.1
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> hbase.version must be updated to address CVE-2018-8025 on branch-2.10.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17225) Update jackson-mapper-asl-1.9.13 to atlassian version to mitigate: CVE-2019-10172
[ https://issues.apache.org/jira/browse/HADOOP-17225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated HADOOP-17225: -- Attachment: HADOOP-17225-002.patch > Update jackson-mapper-asl-1.9.13 to atlassian version to mitigate: > CVE-2019-10172 > - > > Key: HADOOP-17225 > URL: https://issues.apache.org/jira/browse/HADOOP-17225 > Project: Hadoop Common > Issue Type: Bug >Reporter: Brahma Reddy Battula >Assignee: Brahma Reddy Battula >Priority: Major > Attachments: HADOOP-17225-001.patch, HADOOP-17225-002.patch > > > Currently jersey depends on the jackson, and upgradation of jersey from 1.X > to 2.x looks complicated(see HADOOP-15984 and HADOOP-16485). > Update jackson-mapper-asl-1.9.13 to atlassian version to mitigate: > CVE-2019-10172. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17225) Update jackson-mapper-asl-1.9.13 to atlassian version to mitigate: CVE-2019-10172
[ https://issues.apache.org/jira/browse/HADOOP-17225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17419699#comment-17419699 ] Brahma Reddy Battula commented on HADOOP-17225: --- [~aajisaka] thanks for taking a look, updated the patch with latest version. > Update jackson-mapper-asl-1.9.13 to atlassian version to mitigate: > CVE-2019-10172 > - > > Key: HADOOP-17225 > URL: https://issues.apache.org/jira/browse/HADOOP-17225 > Project: Hadoop Common > Issue Type: Bug >Reporter: Brahma Reddy Battula >Assignee: Brahma Reddy Battula >Priority: Major > Attachments: HADOOP-17225-001.patch, HADOOP-17225-002.patch > > > Currently jersey depends on the jackson, and upgradation of jersey from 1.X > to 2.x looks complicated(see HADOOP-15984 and HADOOP-16485). > Update jackson-mapper-asl-1.9.13 to atlassian version to mitigate: > CVE-2019-10172. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17917) Backport HADOOP-15993 to branch-3.2 which address CVE-2014-4611
[ https://issues.apache.org/jira/browse/HADOOP-17917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17419690#comment-17419690 ] Brahma Reddy Battula commented on HADOOP-17917: --- [~aajisaka] thanks for review and commit. > Backport HADOOP-15993 to branch-3.2 which address CVE-2014-4611 > --- > > Key: HADOOP-17917 > URL: https://issues.apache.org/jira/browse/HADOOP-17917 > Project: Hadoop Common > Issue Type: Bug >Reporter: Brahma Reddy Battula >Assignee: Brahma Reddy Battula >Priority: Major > Fix For: 3.2.3 > > Attachments: HADOOP-17917-branch-3.2-001.patch, > HADOOP-17917-branch-3.2-002.patch > > > Now the version is 0.8.2.1 and it has net.jpountz.lz4:lz4:1.2.0 dependency, > which is vulnerable. > ([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-4611]) > > cc./ [~aajisaka] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17917) Backport HADOOP-15993 to branch-3.2 which Address CVE-2014-4611
[ https://issues.apache.org/jira/browse/HADOOP-17917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17417919#comment-17417919 ] Brahma Reddy Battula commented on HADOOP-17917: --- oops, it missed.. thanks for review. Uploaded corrected one. > Backport HADOOP-15993 to branch-3.2 which Address CVE-2014-4611 > --- > > Key: HADOOP-17917 > URL: https://issues.apache.org/jira/browse/HADOOP-17917 > Project: Hadoop Common > Issue Type: Bug >Reporter: Brahma Reddy Battula >Assignee: Brahma Reddy Battula >Priority: Major > Attachments: HADOOP-17917-branch-3.2-001.patch, > HADOOP-17917-branch-3.2-002.patch > > > Now the version is 0.8.2.1 and it has net.jpountz.lz4:lz4:1.2.0 dependency, > which is vulnerable. > ([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-4611]) > > cc./ [~aajisaka] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17917) Backport HADOOP-15993 to branch-3.2 which Address CVE-2014-4611
[ https://issues.apache.org/jira/browse/HADOOP-17917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated HADOOP-17917: -- Attachment: HADOOP-17917-branch-3.2-002.patch > Backport HADOOP-15993 to branch-3.2 which Address CVE-2014-4611 > --- > > Key: HADOOP-17917 > URL: https://issues.apache.org/jira/browse/HADOOP-17917 > Project: Hadoop Common > Issue Type: Bug >Reporter: Brahma Reddy Battula >Assignee: Brahma Reddy Battula >Priority: Major > Attachments: HADOOP-17917-branch-3.2-001.patch, > HADOOP-17917-branch-3.2-002.patch > > > Now the version is 0.8.2.1 and it has net.jpountz.lz4:lz4:1.2.0 dependency, > which is vulnerable. > ([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-4611]) > > cc./ [~aajisaka] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17225) Update jackson-mapper-asl-1.9.13 to atlassian version to mitigate: CVE-2019-10172
[ https://issues.apache.org/jira/browse/HADOOP-17225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17417610#comment-17417610 ] Brahma Reddy Battula commented on HADOOP-17225: --- Planning to push branch-3.2 as this CVE fix.. > Update jackson-mapper-asl-1.9.13 to atlassian version to mitigate: > CVE-2019-10172 > - > > Key: HADOOP-17225 > URL: https://issues.apache.org/jira/browse/HADOOP-17225 > Project: Hadoop Common > Issue Type: Bug >Reporter: Brahma Reddy Battula >Assignee: Brahma Reddy Battula >Priority: Major > Attachments: HADOOP-17225-001.patch > > > Currently jersey depends on the jackson, and upgradation of jersey from 1.X > to 2.x looks complicated(see HADOOP-15984 and HADOOP-16485). > Update jackson-mapper-asl-1.9.13 to atlassian version to mitigate: > CVE-2019-10172. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17917) Backport HADOOP-15993 to branch-3.2 which Address CVE-2014-4611
[ https://issues.apache.org/jira/browse/HADOOP-17917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated HADOOP-17917: -- Status: Patch Available (was: Open) Uploaded patch. [~aajisaka] could you review the same..? > Backport HADOOP-15993 to branch-3.2 which Address CVE-2014-4611 > --- > > Key: HADOOP-17917 > URL: https://issues.apache.org/jira/browse/HADOOP-17917 > Project: Hadoop Common > Issue Type: Bug >Reporter: Brahma Reddy Battula >Assignee: Brahma Reddy Battula >Priority: Major > Attachments: HADOOP-17917-branch-3.2-001.patch > > > Now the version is 0.8.2.1 and it has net.jpountz.lz4:lz4:1.2.0 dependency, > which is vulnerable. > ([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-4611]) > > cc./ [~aajisaka] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17917) Backport HADOOP-15993 to branch-3.2 which Address CVE-2014-4611
[ https://issues.apache.org/jira/browse/HADOOP-17917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated HADOOP-17917: -- Attachment: HADOOP-17917-branch-3.2-001.patch > Backport HADOOP-15993 to branch-3.2 which Address CVE-2014-4611 > --- > > Key: HADOOP-17917 > URL: https://issues.apache.org/jira/browse/HADOOP-17917 > Project: Hadoop Common > Issue Type: Bug >Reporter: Brahma Reddy Battula >Assignee: Brahma Reddy Battula >Priority: Major > Attachments: HADOOP-17917-branch-3.2-001.patch > > > Now the version is 0.8.2.1 and it has net.jpountz.lz4:lz4:1.2.0 dependency, > which is vulnerable. > ([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-4611]) > > cc./ [~aajisaka] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17917) Backport HADOOP-15993 to branch-3.2 which Address CVE-2014-4611
[ https://issues.apache.org/jira/browse/HADOOP-17917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated HADOOP-17917: -- Description: Now the version is 0.8.2.1 and it has net.jpountz.lz4:lz4:1.2.0 dependency, which is vulnerable. ([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-4611]) cc./ [~aajisaka] was:Now the version is 0.8.2.1 and it has net.jpountz.lz4:lz4:1.2.0 dependency, which is vulnerable. ([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-4611]) > Backport HADOOP-15993 to branch-3.2 which Address CVE-2014-4611 > --- > > Key: HADOOP-17917 > URL: https://issues.apache.org/jira/browse/HADOOP-17917 > Project: Hadoop Common > Issue Type: Bug >Reporter: Brahma Reddy Battula >Assignee: Brahma Reddy Battula >Priority: Major > > Now the version is 0.8.2.1 and it has net.jpountz.lz4:lz4:1.2.0 dependency, > which is vulnerable. > ([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-4611]) > > cc./ [~aajisaka] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Created] (HADOOP-17917) Backport HADOOP-15993 to branch-3.2 which Address CVE-2014-4611
Brahma Reddy Battula created HADOOP-17917: - Summary: Backport HADOOP-15993 to branch-3.2 which Address CVE-2014-4611 Key: HADOOP-17917 URL: https://issues.apache.org/jira/browse/HADOOP-17917 Project: Hadoop Common Issue Type: Bug Reporter: Brahma Reddy Battula Assignee: Brahma Reddy Battula Now the version is 0.8.2.1 and it has net.jpountz.lz4:lz4:1.2.0 dependency, which is vulnerable. ([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-4611]) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17225) Update jackson-mapper-asl-1.9.13 to atlassian version to mitigate: CVE-2019-10172
[ https://issues.apache.org/jira/browse/HADOOP-17225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17410915#comment-17410915 ] Brahma Reddy Battula commented on HADOOP-17225: --- Yes...waiting for somebody review. > Update jackson-mapper-asl-1.9.13 to atlassian version to mitigate: > CVE-2019-10172 > - > > Key: HADOOP-17225 > URL: https://issues.apache.org/jira/browse/HADOOP-17225 > Project: Hadoop Common > Issue Type: Bug >Reporter: Brahma Reddy Battula >Assignee: Brahma Reddy Battula >Priority: Major > Attachments: HADOOP-17225-001.patch > > > Currently jersey depends on the jackson, and upgradation of jersey from 1.X > to 2.x looks complicated(see HADOOP-15984 and HADOOP-16485). > Update jackson-mapper-asl-1.9.13 to atlassian version to mitigate: > CVE-2019-10172. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-14922) Build of Mapreduce Native Task module fails with unknown opcode "bswap"
[ https://issues.apache.org/jira/browse/HADOOP-14922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17403796#comment-17403796 ] Brahma Reddy Battula commented on HADOOP-14922: --- [~iwasakims] are you planning commit to branch-3.2..? > Build of Mapreduce Native Task module fails with unknown opcode "bswap" > --- > > Key: HADOOP-14922 > URL: https://issues.apache.org/jira/browse/HADOOP-14922 > Project: Hadoop Common > Issue Type: Bug >Affects Versions: 3.0.0-alpha3 > Environment: OS: Ubuntu 14.04 > Arch: PPC64LE >Reporter: Anup Halarnkar >Assignee: Anup Halarnkar >Priority: Major > Fix For: 3.4.0 > > Attachments: HADOOP-14922.01.patch > > > [WARNING] /tmp/cckBBdQp.s: Assembler messages: > [WARNING] /tmp/cckBBdQp.s:3127: Error: unrecognized opcode: `bswap' > [WARNING] /tmp/cckBBdQp.s:3152: Error: unrecognized opcode: `bswap' > [WARNING] make[2]: *** > [CMakeFiles/nativetask.dir/main/native/src/codec/BlockCodec.cc.o] Error 1 > [WARNING] make[2]: *** Waiting for unfinished jobs > [WARNING] /tmp/ccqRfBZp.s: Assembler messages: > [WARNING] /tmp/ccqRfBZp.s:2098: Error: unrecognized opcode: `bswap' > [WARNING] /tmp/ccqRfBZp.s:2123: Error: unrecognized opcode: `bswap' > [WARNING] make[2]: *** > [CMakeFiles/nativetask.dir/main/native/src/codec/Lz4Codec.cc.o] Error 1 > [WARNING] /tmp/cc50B5Mp.s: Assembler messages: > [WARNING] /tmp/cc50B5Mp.s:3112: Error: unrecognized opcode: `bswap' > [WARNING] /tmp/cc50B5Mp.s:3137: Error: unrecognized opcode: `bswap' > [WARNING] make[2]: *** > [CMakeFiles/nativetask_static.dir/main/native/src/codec/BlockCodec.cc.o] > Error 1 > [WARNING] make[2]: *** Waiting for unfinished jobs > [WARNING] /tmp/ccobJqOY.s: Assembler messages: > [WARNING] /tmp/ccobJqOY.s:2098: Error: unrecognized opcode: `bswap' > [WARNING] /tmp/ccobJqOY.s:2123: Error: unrecognized opcode: `bswap' > [WARNING] make[2]: *** > [CMakeFiles/nativetask_static.dir/main/native/src/codec/Lz4Codec.cc.o] Error 1 > [WARNING] /tmp/ccdaQ1CY.s: Assembler messages: > [WARNING] /tmp/ccdaQ1CY.s:2235: Error: unrecognized opcode: `bswap' > [WARNING] /tmp/ccdaQ1CY.s:2249: Error: unrecognized opcode: `bswap' > [WARNING] /tmp/ccRwHt5X.s: Assembler messages: > [WARNING] /tmp/ccRwHt5X.s:2235: Error: unrecognized opcode: `bswap' > [WARNING] /tmp/ccRwHt5X.s:2249: Error: unrecognized opcode: `bswap' > [WARNING] make[2]: *** > [CMakeFiles/nativetask.dir/main/native/src/codec/SnappyCodec.cc.o] Error 1 > [WARNING] make[1]: *** [CMakeFiles/nativetask.dir/all] Error 2 > [WARNING] make[1]: *** Waiting for unfinished jobs > [WARNING] make[2]: *** > [CMakeFiles/nativetask_static.dir/main/native/src/codec/SnappyCodec.cc.o] > Error 1 > [WARNING] make[1]: *** [CMakeFiles/nativetask_static.dir/all] Error 2 > [WARNING] make: *** [all] Error 2 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17849) Exclude spotbugs-annotations from transitive dependencies on branch-3.2
[
https://issues.apache.org/jira/browse/HADOOP-17849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17399914#comment-17399914
]
Brahma Reddy Battula commented on HADOOP-17849:
---
{quote}[~brahmareddy] This is for users or downstream products using the
combination of hadoop-3.2.x and zookeeper-3.4.14 since ZooKeeper 3.4.14 newly
introduced the dependency on com.github.spotbugs:spotbugs-annotations.
{quote}
So, this will issue will pop up when we change zookeeper to 3.4.14 ?.
{quote}Now ZooKeeper 3.4.13 is used in branch-3.2. I suppose we need to upgrade
the version to 3.4.14 due to CVE-2019-0201
([https://zookeeper.apache.org/security.html]).
{quote}
Ok. so, first we change this and commit this jira.
Looks this already merged, are you planning raise PR for branch-3.2.3 also..?
> Exclude spotbugs-annotations from transitive dependencies on branch-3.2
> ---
>
> Key: HADOOP-17849
> URL: https://issues.apache.org/jira/browse/HADOOP-17849
> Project: Hadoop Common
> Issue Type: Improvement
>Affects Versions: 3.2.2
>Reporter: Masatake Iwasaki
>Assignee: Masatake Iwasaki
>Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Building Hadoop in dist profile with ZooKeeper 3.4.14 fails on
> hadoop-client-check-test-invariants. Excluding
> com.github.spotbugs:spotbugs-annotation from transitive dependencies should
> fix this for users needing zookeeer-3.4.14. Since the dependency is
> provided/optional on ZooKeeper 3.5.x, branch-3.3 and above are not affected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17849) Exclude spotbugs-annotations from transitive dependencies on branch-3.2
[ https://issues.apache.org/jira/browse/HADOOP-17849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17399599#comment-17399599 ] Brahma Reddy Battula commented on HADOOP-17849: --- Hi [~iwasakims]. why this issue is surfacing now ( are we using bigtop on branch-3.2 now..?) ,this was there when we introduce spotbug plugin,isn't it..? can you more background..? > Exclude spotbugs-annotations from transitive dependencies on branch-3.2 > --- > > Key: HADOOP-17849 > URL: https://issues.apache.org/jira/browse/HADOOP-17849 > Project: Hadoop Common > Issue Type: Improvement >Affects Versions: 3.2.2 >Reporter: Masatake Iwasaki >Assignee: Masatake Iwasaki >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > Building Hadoop in dist profile with ZooKeeper 3.4.14 fails on > hadoop-client-check-test-invariants. Excluding > com.github.spotbugs:spotbugs-annotation from transitive dependencies should > fix this for users needing zookeeer-3.4.14. Since the dependency is > provided/optional on ZooKeeper 3.5.x, branch-3.3 and above are not affected. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17370) Upgrade commons-compress to 1.21
[ https://issues.apache.org/jira/browse/HADOOP-17370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17395563#comment-17395563 ] Brahma Reddy Battula commented on HADOOP-17370: --- [~aajisaka] thanks > Upgrade commons-compress to 1.21 > > > Key: HADOOP-17370 > URL: https://issues.apache.org/jira/browse/HADOOP-17370 > Project: Hadoop Common > Issue Type: Bug > Components: common >Affects Versions: 3.3.0, 3.2.1 >Reporter: Dongjoon Hyun >Assignee: Akira Ajisaka >Priority: Major > Labels: pull-request-available > Fix For: 3.4.0, 2.10.2, 3.2.3, 3.3.2 > > Time Spent: 4h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-17840) Backport HADOOP-17837 to branch-3.2
[ https://issues.apache.org/jira/browse/HADOOP-17840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula resolved HADOOP-17840. --- Fix Version/s: 3.2.3 Hadoop Flags: Reviewed Resolution: Fixed Committed to branch-3.2.3...[~bbeaudreault] thanks for your contribution. > Backport HADOOP-17837 to branch-3.2 > --- > > Key: HADOOP-17840 > URL: https://issues.apache.org/jira/browse/HADOOP-17840 > Project: Hadoop Common > Issue Type: Sub-task >Reporter: Bryan Beaudreault >Assignee: Bryan Beaudreault >Priority: Minor > Labels: pull-request-available > Fix For: 3.2.3 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-17837) Make it easier to debug UnknownHostExceptions from NetUtils.connect
[ https://issues.apache.org/jira/browse/HADOOP-17837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula resolved HADOOP-17837. --- Hadoop Flags: Reviewed Resolution: Fixed [~bbeaudreault] thanks raising the PR. Committed to trunk and branch-3.3.. As this only test assertion, ran locally and pushed. > Make it easier to debug UnknownHostExceptions from NetUtils.connect > --- > > Key: HADOOP-17837 > URL: https://issues.apache.org/jira/browse/HADOOP-17837 > Project: Hadoop Common > Issue Type: Improvement >Reporter: Bryan Beaudreault >Assignee: Bryan Beaudreault >Priority: Minor > Labels: pull-request-available > Fix For: 3.4.0, 3.3.2 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Most UnknownHostExceptions thrown throughout hadoop include a useful message, > either the hostname that was not found or some other descriptor of the > problem. The UnknownHostException thrown from NetUtils.connect only includes > the [message of the underlying > UnresolvedAddressException|https://github.com/apache/hadoop/blob/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/net/NetUtils.java#L592]. > If you take a look at the source for UnresolvedAddressException, [it only > has a no-args > constructor|https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/nio/channels/UnresolvedAddressException.html] > (java11, but same is true in other versions). So it never has a message, > meaning the UnknownHostException message is empty. > We should include the endpoint.toString() in the UnknownHostException thrown > by NetUtils.connect -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17370) Upgrade commons-compress to 1.21
[ https://issues.apache.org/jira/browse/HADOOP-17370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17394851#comment-17394851 ] Brahma Reddy Battula commented on HADOOP-17370: --- [~aajisaka] thanks addressing this issue. Looks PR #2452 is closed by mentioning that there are so many test case failures.. could please confirm the same..? and license file also updated. > Upgrade commons-compress to 1.21 > > > Key: HADOOP-17370 > URL: https://issues.apache.org/jira/browse/HADOOP-17370 > Project: Hadoop Common > Issue Type: Bug > Components: common >Affects Versions: 3.3.0, 3.2.1 >Reporter: Dongjoon Hyun >Assignee: Akira Ajisaka >Priority: Major > Labels: pull-request-available > Time Spent: 2h 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-16752) ABFS: test failure testLastModifiedTime()
[ https://issues.apache.org/jira/browse/HADOOP-16752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17394839#comment-17394839 ] Brahma Reddy Battula commented on HADOOP-16752: --- HI [~DanielZhou] and [~ste...@apache.org] Target version given as 3.2.2 which is already released.. can you guys planning to target to 3.2.3..? Please let me know, I am planing to cut the release for 3.2.3 > ABFS: test failure testLastModifiedTime() > - > > Key: HADOOP-16752 > URL: https://issues.apache.org/jira/browse/HADOOP-16752 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/azure >Reporter: Da Zhou >Assignee: Sneha Vijayarajan >Priority: Major > Labels: pull-request-available > Time Spent: 1h 20m > Remaining Estimate: 0h > > java.lang.AssertionError: lastModifiedTime should be after minCreateStartTime > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.assertTrue(Assert.java:41) > at > org.apache.hadoop.fs.azurebfs.ITestAzureBlobFileSystemFileStatus.testLastModifiedTime(ITestAzureBlobFileSystemFileStatus.java:138) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > at > org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298) > at > org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17708) Fail to build hadoop-common from source on Fedora
[
https://issues.apache.org/jira/browse/HADOOP-17708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17394836#comment-17394836
]
Brahma Reddy Battula commented on HADOOP-17708:
---
[~bioinfornatics] did you apply patch as suggested by [~iwasakims] and ran
again..? Currently i removed the target version 3.2.2 which released.
> Fail to build hadoop-common from source on Fedora
> -
>
> Key: HADOOP-17708
> URL: https://issues.apache.org/jira/browse/HADOOP-17708
> Project: Hadoop Common
> Issue Type: Bug
>Reporter: Jonathan mercier
>Priority: Major
>
> Dear I tried to build hadoop from source with a vanilla fedora 34
> {code:bash}
> dnf group install -y "Development Tools" \
> && dnf install -y java-1.8.0-openjdk-devel fuse-devel snappy-java
> snappy-devel jansson-devel protobuf zlib-devel libzstd-devel \
>maven-1:3.6.3 cmake gcc-c++ ant protobuf-compiler
> protobuf-java slf4j
> export JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.292.b10-0.fc34.x86_64/
> export MAVEN_OPTS="-Xms2048M -Xmx4096M"
> export
> PATH="/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.292.b10-0.fc34.x86_64/bin/:$PATH"
> export CC=/usr/bin/gcc
> export CXX=/usr/bin/g++
> curl -LO
> https://apache.mediamirrors.org/hadoop/common/hadoop-3.2.2/hadoop-3.2.2-src.tar.gz
> tar xf hadoop-3.2.2-src.tar.gz && cd hadoop-3.2.2-src
> mvn package -Pdist,native -Drequire.snappy=true -DskipTests -Dtar
> {code}
> But I have this error
> {code:java}
> at org.apache.hadoop.maven.plugin.cmakebuilder.CompileMojo.runMake
> (CompileMojo.java:229)
>
>
> at org.apache.hadoop.maven.plugin.cmakebuilder.CompileMojo.execute
> (CompileMojo.java:98)
>
>
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
>
>
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
>
>
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
>
>
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
>
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
>
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
>
>
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
>
>
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
>
>
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
>
>
>
> at
[jira] [Updated] (HADOOP-17708) Fail to build hadoop-common from source on Fedora
[
https://issues.apache.org/jira/browse/HADOOP-17708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brahma Reddy Battula updated HADOOP-17708:
--
Target Version/s: (was: 3.2.2)
> Fail to build hadoop-common from source on Fedora
> -
>
> Key: HADOOP-17708
> URL: https://issues.apache.org/jira/browse/HADOOP-17708
> Project: Hadoop Common
> Issue Type: Bug
>Reporter: Jonathan mercier
>Priority: Major
>
> Dear I tried to build hadoop from source with a vanilla fedora 34
> {code:bash}
> dnf group install -y "Development Tools" \
> && dnf install -y java-1.8.0-openjdk-devel fuse-devel snappy-java
> snappy-devel jansson-devel protobuf zlib-devel libzstd-devel \
>maven-1:3.6.3 cmake gcc-c++ ant protobuf-compiler
> protobuf-java slf4j
> export JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.292.b10-0.fc34.x86_64/
> export MAVEN_OPTS="-Xms2048M -Xmx4096M"
> export
> PATH="/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.292.b10-0.fc34.x86_64/bin/:$PATH"
> export CC=/usr/bin/gcc
> export CXX=/usr/bin/g++
> curl -LO
> https://apache.mediamirrors.org/hadoop/common/hadoop-3.2.2/hadoop-3.2.2-src.tar.gz
> tar xf hadoop-3.2.2-src.tar.gz && cd hadoop-3.2.2-src
> mvn package -Pdist,native -Drequire.snappy=true -DskipTests -Dtar
> {code}
> But I have this error
> {code:java}
> at org.apache.hadoop.maven.plugin.cmakebuilder.CompileMojo.runMake
> (CompileMojo.java:229)
>
>
> at org.apache.hadoop.maven.plugin.cmakebuilder.CompileMojo.execute
> (CompileMojo.java:98)
>
>
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
>
>
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
>
>
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
>
>
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
>
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
>
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
>
>
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
>
>
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
>
>
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
>
>
>
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
>
>
[jira] [Commented] (HADOOP-17840) Backport HADOOP-17837 to branch-3.2
[ https://issues.apache.org/jira/browse/HADOOP-17840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17394822#comment-17394822 ] Brahma Reddy Battula commented on HADOOP-17840: --- [~bbeaudreault] for branch-3.2 you can update here.. and for trunk, you can upload the testutil change to same jira as a addendum patch. > Backport HADOOP-17837 to branch-3.2 > --- > > Key: HADOOP-17840 > URL: https://issues.apache.org/jira/browse/HADOOP-17840 > Project: Hadoop Common > Issue Type: Sub-task >Reporter: Bryan Beaudreault >Assignee: Bryan Beaudreault >Priority: Minor > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17840) Backport HADOOP-17837 to branch-3.2
[ https://issues.apache.org/jira/browse/HADOOP-17840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17394732#comment-17394732 ] Brahma Reddy Battula commented on HADOOP-17840: --- [~bbeaudreault] thanks reporting, I thought of cherry-pick this but looks [~ste...@apache.org] has some comments previous PR.. Can you please address those..? > Backport HADOOP-17837 to branch-3.2 > --- > > Key: HADOOP-17840 > URL: https://issues.apache.org/jira/browse/HADOOP-17840 > Project: Hadoop Common > Issue Type: Sub-task >Reporter: Bryan Beaudreault >Assignee: Bryan Beaudreault >Priority: Minor > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-12670) Fix TestNetUtils and TestSecurityUtil when localhost is ipv6 only
[
https://issues.apache.org/jira/browse/HADOOP-12670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brahma Reddy Battula updated HADOOP-12670:
--
Fix Version/s: HADOOP-17800
Hadoop Flags: Reviewed
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to branch HADOOP-17800. [~eclark] and [~hemanthboyina] thanks for
your contribution.
> Fix TestNetUtils and TestSecurityUtil when localhost is ipv6 only
> -
>
> Key: HADOOP-12670
> URL: https://issues.apache.org/jira/browse/HADOOP-12670
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: net
>Affects Versions: HADOOP-11890
>Reporter: Elliott Neil Clark
>Assignee: Elliott Neil Clark
>Priority: Major
> Fix For: HADOOP-17800
>
> Attachments: HADOOP-12670-HADOOP-11890.0.patch,
> HADOOP-12670-HADOOP-11890.2.patch, HADOOP-12670-HADOOP-11890.3.patch,
> HADOOP-12670-HADOOP-17800.001.patch, HADOOP-12670-HADOOP-17800.002.patch
>
>
> {code}
> TestSecurityUtil.testBuildTokenServiceSockAddr:165
> expected:<[127.0.0.]1:123> but was:<[0:0:0:0:0:0:0:]1:123>
> TestSecurityUtil.testBuildDTServiceName:148 expected:<[127.0.0.]1:123> but
> was:<[0:0:0:0:0:0:0:]1:123>
>
> TestSecurityUtil.testSocketAddrWithName:326->verifyServiceAddr:304->verifyAddress:284->verifyValues:251
> expected:<[127.0.0.]1> but was:<[0:0:0:0:0:0:0:]1>
>
> TestSecurityUtil.testSocketAddrWithIP:333->verifyServiceAddr:304->verifyAddress:284->verifyValues:251
> expected:<[127.0.0.]1> but was:<[0:0:0:0:0:0:0:]1>
>
> TestSecurityUtil.testSocketAddrWithNameToStaticName:340->verifyServiceAddr:304->verifyAddress:284->verifyValues:251
> expected:<[127.0.0.]1> but was:<[0:0:0:0:0:0:0:]1>
> TestNetUtils.testNormalizeHostName:639 expected:<[0:0:0:0:0:0:0:]1> but
> was:<[127.0.0.]1>
> TestNetUtils.testResolverLoopback:533->verifyInetAddress:496
> expected:<[127.0.0.]1> but was:<[0:0:0:0:0:0:0:]1>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-12670) Fix TestNetUtils and TestSecurityUtil when localhost is ipv6 only
[
https://issues.apache.org/jira/browse/HADOOP-12670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17390996#comment-17390996
]
Brahma Reddy Battula commented on HADOOP-12670:
---
[~hemanthboyina] thanks for uploading the patch. Patch lgtm.
> Fix TestNetUtils and TestSecurityUtil when localhost is ipv6 only
> -
>
> Key: HADOOP-12670
> URL: https://issues.apache.org/jira/browse/HADOOP-12670
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: net
>Affects Versions: HADOOP-11890
>Reporter: Elliott Neil Clark
>Assignee: Elliott Neil Clark
>Priority: Major
> Attachments: HADOOP-12670-HADOOP-11890.0.patch,
> HADOOP-12670-HADOOP-11890.2.patch, HADOOP-12670-HADOOP-11890.3.patch,
> HADOOP-12670-HADOOP-17800.001.patch, HADOOP-12670-HADOOP-17800.002.patch
>
>
> {code}
> TestSecurityUtil.testBuildTokenServiceSockAddr:165
> expected:<[127.0.0.]1:123> but was:<[0:0:0:0:0:0:0:]1:123>
> TestSecurityUtil.testBuildDTServiceName:148 expected:<[127.0.0.]1:123> but
> was:<[0:0:0:0:0:0:0:]1:123>
>
> TestSecurityUtil.testSocketAddrWithName:326->verifyServiceAddr:304->verifyAddress:284->verifyValues:251
> expected:<[127.0.0.]1> but was:<[0:0:0:0:0:0:0:]1>
>
> TestSecurityUtil.testSocketAddrWithIP:333->verifyServiceAddr:304->verifyAddress:284->verifyValues:251
> expected:<[127.0.0.]1> but was:<[0:0:0:0:0:0:0:]1>
>
> TestSecurityUtil.testSocketAddrWithNameToStaticName:340->verifyServiceAddr:304->verifyAddress:284->verifyValues:251
> expected:<[127.0.0.]1> but was:<[0:0:0:0:0:0:0:]1>
> TestNetUtils.testNormalizeHostName:639 expected:<[0:0:0:0:0:0:0:]1> but
> was:<[127.0.0.]1>
> TestNetUtils.testResolverLoopback:533->verifyInetAddress:496
> expected:<[127.0.0.]1> but was:<[0:0:0:0:0:0:0:]1>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-12432) Add support for include/exclude lists on IPv6 setup
[ https://issues.apache.org/jira/browse/HADOOP-12432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated HADOOP-12432: -- Fix Version/s: HADOOP-17800 Hadoop Flags: Reviewed Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch. [~newanja] and [~hemanthboyina] thanks for contribution. > Add support for include/exclude lists on IPv6 setup > --- > > Key: HADOOP-12432 > URL: https://issues.apache.org/jira/browse/HADOOP-12432 > Project: Hadoop Common > Issue Type: Sub-task >Affects Versions: 3.0.0-alpha1 > Environment: This affects only IPv6 cluster setup >Reporter: Nemanja Matkovic >Assignee: Nemanja Matkovic >Priority: Major > Labels: ipv6 > Fix For: HADOOP-11890, HADOOP-17800 > > Attachments: HADOOP-12432-HADOOP-11890.1.patch, > HADOOP-12432-HADOOP-17800.001.patch, HADOOP-12432-trunk.patch, > HADOOP-12432.1.patch, HADOOP-12432.2.patch, HADOOP-12432.3.patch, > HDFS-8078.15_plus_HDFS-9026.patch, HDFS-9026-1.patch, HDFS-9026-2.patch, > HDFS-9026-HADOOP-11890.002.patch > > Original Estimate: 168h > Remaining Estimate: 168h > > This is a tracking item for having e2e IPv6 support in HDFS. > Nate did great ground work in HDFS-8078 but for having whole feature working > e2e this one of the items missing. > Basically today NN won't be able to parse IPv6 addresses if they are present > in include or exclude list. > Patch has a dependency (and has been tested on IPv6 only cluster) on top of > HDFS-8078.14.patch > This should be committed to HADOOP-11890 branch. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-12432) Add support for include/exclude lists on IPv6 setup
[ https://issues.apache.org/jira/browse/HADOOP-12432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17390252#comment-17390252 ] Brahma Reddy Battula commented on HADOOP-12432: --- [~hemanthboyina] thanks for uploading the patch. HADOOP-12432-HADOOP-17800.001.patch lgtm. > Add support for include/exclude lists on IPv6 setup > --- > > Key: HADOOP-12432 > URL: https://issues.apache.org/jira/browse/HADOOP-12432 > Project: Hadoop Common > Issue Type: Sub-task >Affects Versions: 3.0.0-alpha1 > Environment: This affects only IPv6 cluster setup >Reporter: Nemanja Matkovic >Assignee: Nemanja Matkovic >Priority: Major > Labels: ipv6 > Fix For: HADOOP-11890 > > Attachments: HADOOP-12432-HADOOP-11890.1.patch, > HADOOP-12432-HADOOP-17800.001.patch, HADOOP-12432-trunk.patch, > HADOOP-12432.1.patch, HADOOP-12432.2.patch, HADOOP-12432.3.patch, > HDFS-8078.15_plus_HDFS-9026.patch, HDFS-9026-1.patch, HDFS-9026-2.patch, > HDFS-9026-HADOOP-11890.002.patch > > Original Estimate: 168h > Remaining Estimate: 168h > > This is a tracking item for having e2e IPv6 support in HDFS. > Nate did great ground work in HDFS-8078 but for having whole feature working > e2e this one of the items missing. > Basically today NN won't be able to parse IPv6 addresses if they are present > in include or exclude list. > Patch has a dependency (and has been tested on IPv6 only cluster) on top of > HDFS-8078.14.patch > This should be committed to HADOOP-11890 branch. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-12491) Hadoop-common - Avoid unsafe split and append on fields that might be IPv6 literals
[ https://issues.apache.org/jira/browse/HADOOP-12491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated HADOOP-12491: -- Fix Version/s: HADOOP-17800 Hadoop Flags: Reviewed Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch HADOOP-17800. Thanks all. > Hadoop-common - Avoid unsafe split and append on fields that might be IPv6 > literals > --- > > Key: HADOOP-12491 > URL: https://issues.apache.org/jira/browse/HADOOP-12491 > Project: Hadoop Common > Issue Type: Sub-task >Affects Versions: HADOOP-11890 >Reporter: Nemanja Matkovic >Assignee: Nemanja Matkovic >Priority: Major > Labels: ipv6 > Fix For: HADOOP-11890, HADOOP-17800 > > Attachments: HADOOP-12491-HADOOP-11890.1.patch, > HADOOP-12491-HADOOP-11890.2.patch, HADOOP-12491-HADOOP-17800.001.patch, > HADOOP-12491-HADOOP-17800.002.patch, HADOOP-12491-HADOOP-17800.003.patch, > HADOOP-12491-HADOOP-17800.004.patch > > Original Estimate: 48h > Remaining Estimate: 48h > > Hadoop-common portion of HADOOP-12122 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-12430) Fix HDFS client gets errors trying to to connect to IPv6 DataNode
[ https://issues.apache.org/jira/browse/HADOOP-12430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated HADOOP-12430: -- Fix Version/s: HADOOP-11890 > Fix HDFS client gets errors trying to to connect to IPv6 DataNode > - > > Key: HADOOP-12430 > URL: https://issues.apache.org/jira/browse/HADOOP-12430 > Project: Hadoop Common > Issue Type: Sub-task >Affects Versions: 2.6.0 >Reporter: Nate Edel >Assignee: Nate Edel >Priority: Major > Labels: BB2015-05-TBR, ipv6 > Fix For: HADOOP-11890, HADOOP-17800 > > Attachments: HDFS-8078-HADOOP-17800.001.patch, > HDFS-8078-HADOOP-17800.002.patch, HDFS-8078.10.patch, HDFS-8078.11.patch, > HDFS-8078.12.patch, HDFS-8078.13.patch, HDFS-8078.14.patch, > HDFS-8078.15.patch, HDFS-8078.9.patch, dummy.patch > > > 1st exception, on put: > 15/03/23 18:43:18 WARN hdfs.DFSClient: DataStreamer Exception > java.lang.IllegalArgumentException: Does not contain a valid host:port > authority: 2401:db00:1010:70ba:face:0:8:0:50010 > at org.apache.hadoop.net.NetUtils.createSocketAddr(NetUtils.java:212) > at org.apache.hadoop.net.NetUtils.createSocketAddr(NetUtils.java:164) > at org.apache.hadoop.net.NetUtils.createSocketAddr(NetUtils.java:153) > at > org.apache.hadoop.hdfs.DFSOutputStream.createSocketForPipeline(DFSOutputStream.java:1607) > at > org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.createBlockOutputStream(DFSOutputStream.java:1408) > at > org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.nextBlockOutputStream(DFSOutputStream.java:1361) > at > org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.run(DFSOutputStream.java:588) > Appears to actually stem from code in DataNodeID which assumes it's safe to > append together (ipaddr + ":" + port) -- which is OK for IPv4 and not OK for > IPv6. NetUtils.createSocketAddr( ) assembles a Java URI object, which > requires the format proto://[2401:db00:1010:70ba:face:0:8:0]:50010 > Currently using InetAddress.getByName() to validate IPv6 (guava > InetAddresses.forString has been flaky) but could also use our own parsing. > (From logging this, it seems like a low-enough frequency call that the extra > object creation shouldn't be problematic, and for me the slight risk of > passing in bad input that is not actually an IPv4 or IPv6 address and thus > calling an external DNS lookup is outweighed by getting the address > normalized and avoiding rewriting parsing.) > Alternatively, sun.net.util.IPAddressUtil.isIPv6LiteralAddress() > --- > 2nd exception (on datanode) > 15/04/13 13:18:07 ERROR datanode.DataNode: > dev1903.prn1.facebook.com:50010:DataXceiver error processing unknown > operation src: /2401:db00:20:7013:face:0:7:0:54152 dst: > /2401:db00:11:d010:face:0:2f:0:50010 > java.io.EOFException > at java.io.DataInputStream.readShort(DataInputStream.java:315) > at > org.apache.hadoop.hdfs.protocol.datatransfer.Receiver.readOp(Receiver.java:58) > at > org.apache.hadoop.hdfs.server.datanode.DataXceiver.run(DataXceiver.java:226) > at java.lang.Thread.run(Thread.java:745) > Which also comes as client error "-get: 2401 is not an IP string literal." > This one has existing parsing logic which needs to shift to the last colon > rather than the first. Should also be a tiny bit faster by using lastIndexOf > rather than split. Could alternatively use the techniques above. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-12491) Hadoop-common - Avoid unsafe split and append on fields that might be IPv6 literals
[ https://issues.apache.org/jira/browse/HADOOP-12491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17390242#comment-17390242 ] Brahma Reddy Battula commented on HADOOP-12491: --- [~hemanthboyina] thanks for uploading to address the checkstyle.. Will commit > Hadoop-common - Avoid unsafe split and append on fields that might be IPv6 > literals > --- > > Key: HADOOP-12491 > URL: https://issues.apache.org/jira/browse/HADOOP-12491 > Project: Hadoop Common > Issue Type: Sub-task >Affects Versions: HADOOP-11890 >Reporter: Nemanja Matkovic >Assignee: Nemanja Matkovic >Priority: Major > Labels: ipv6 > Fix For: HADOOP-11890 > > Attachments: HADOOP-12491-HADOOP-11890.1.patch, > HADOOP-12491-HADOOP-11890.2.patch, HADOOP-12491-HADOOP-17800.001.patch, > HADOOP-12491-HADOOP-17800.002.patch, HADOOP-12491-HADOOP-17800.003.patch, > HADOOP-12491-HADOOP-17800.004.patch > > Original Estimate: 48h > Remaining Estimate: 48h > > Hadoop-common portion of HADOOP-12122 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-12491) Hadoop-common - Avoid unsafe split and append on fields that might be IPv6 literals
[ https://issues.apache.org/jira/browse/HADOOP-12491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17388491#comment-17388491 ] Brahma Reddy Battula commented on HADOOP-12491: --- [~hemanthboyina] thanks for uploading, lgtm, can you address the checkstyle..? > Hadoop-common - Avoid unsafe split and append on fields that might be IPv6 > literals > --- > > Key: HADOOP-12491 > URL: https://issues.apache.org/jira/browse/HADOOP-12491 > Project: Hadoop Common > Issue Type: Sub-task >Affects Versions: HADOOP-11890 >Reporter: Nemanja Matkovic >Assignee: Nemanja Matkovic >Priority: Major > Labels: ipv6 > Fix For: HADOOP-11890 > > Attachments: HADOOP-12491-HADOOP-11890.1.patch, > HADOOP-12491-HADOOP-11890.2.patch, HADOOP-12491-HADOOP-17800.001.patch > > Original Estimate: 48h > Remaining Estimate: 48h > > Hadoop-common portion of HADOOP-12122 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-12430) Fix HDFS client gets errors trying to to connect to IPv6 DataNode
[ https://issues.apache.org/jira/browse/HADOOP-12430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated HADOOP-12430: -- Fix Version/s: HADOOP-17800 Hadoop Flags: Reviewed Resolution: Fixed Status: Resolved (was: Patch Available) [~hemanthboyina] thanks confirmation and contribution .. Committed to HADOOP-17800 branch. > Fix HDFS client gets errors trying to to connect to IPv6 DataNode > - > > Key: HADOOP-12430 > URL: https://issues.apache.org/jira/browse/HADOOP-12430 > Project: Hadoop Common > Issue Type: Sub-task >Affects Versions: 2.6.0 >Reporter: Nate Edel >Assignee: Nate Edel >Priority: Major > Labels: BB2015-05-TBR, ipv6 > Fix For: HADOOP-17800 > > Attachments: HDFS-8078-HADOOP-17800.001.patch, > HDFS-8078-HADOOP-17800.002.patch, HDFS-8078.10.patch, HDFS-8078.11.patch, > HDFS-8078.12.patch, HDFS-8078.13.patch, HDFS-8078.14.patch, > HDFS-8078.15.patch, HDFS-8078.9.patch, dummy.patch > > > 1st exception, on put: > 15/03/23 18:43:18 WARN hdfs.DFSClient: DataStreamer Exception > java.lang.IllegalArgumentException: Does not contain a valid host:port > authority: 2401:db00:1010:70ba:face:0:8:0:50010 > at org.apache.hadoop.net.NetUtils.createSocketAddr(NetUtils.java:212) > at org.apache.hadoop.net.NetUtils.createSocketAddr(NetUtils.java:164) > at org.apache.hadoop.net.NetUtils.createSocketAddr(NetUtils.java:153) > at > org.apache.hadoop.hdfs.DFSOutputStream.createSocketForPipeline(DFSOutputStream.java:1607) > at > org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.createBlockOutputStream(DFSOutputStream.java:1408) > at > org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.nextBlockOutputStream(DFSOutputStream.java:1361) > at > org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.run(DFSOutputStream.java:588) > Appears to actually stem from code in DataNodeID which assumes it's safe to > append together (ipaddr + ":" + port) -- which is OK for IPv4 and not OK for > IPv6. NetUtils.createSocketAddr( ) assembles a Java URI object, which > requires the format proto://[2401:db00:1010:70ba:face:0:8:0]:50010 > Currently using InetAddress.getByName() to validate IPv6 (guava > InetAddresses.forString has been flaky) but could also use our own parsing. > (From logging this, it seems like a low-enough frequency call that the extra > object creation shouldn't be problematic, and for me the slight risk of > passing in bad input that is not actually an IPv4 or IPv6 address and thus > calling an external DNS lookup is outweighed by getting the address > normalized and avoiding rewriting parsing.) > Alternatively, sun.net.util.IPAddressUtil.isIPv6LiteralAddress() > --- > 2nd exception (on datanode) > 15/04/13 13:18:07 ERROR datanode.DataNode: > dev1903.prn1.facebook.com:50010:DataXceiver error processing unknown > operation src: /2401:db00:20:7013:face:0:7:0:54152 dst: > /2401:db00:11:d010:face:0:2f:0:50010 > java.io.EOFException > at java.io.DataInputStream.readShort(DataInputStream.java:315) > at > org.apache.hadoop.hdfs.protocol.datatransfer.Receiver.readOp(Receiver.java:58) > at > org.apache.hadoop.hdfs.server.datanode.DataXceiver.run(DataXceiver.java:226) > at java.lang.Thread.run(Thread.java:745) > Which also comes as client error "-get: 2401 is not an IP string literal." > This one has existing parsing logic which needs to shift to the last colon > rather than the first. Should also be a tiny bit faster by using lastIndexOf > rather than split. Could alternatively use the techniques above. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-12430) Fix HDFS client gets errors trying to to connect to IPv6 DataNode
[ https://issues.apache.org/jira/browse/HADOOP-12430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17387266#comment-17387266 ] Brahma Reddy Battula commented on HADOOP-12430: --- [~hemanthboyina] thanks for uploading the patch.. Patch lgtm.. Can you address the test failures. > Fix HDFS client gets errors trying to to connect to IPv6 DataNode > - > > Key: HADOOP-12430 > URL: https://issues.apache.org/jira/browse/HADOOP-12430 > Project: Hadoop Common > Issue Type: Sub-task >Affects Versions: 2.6.0 >Reporter: Nate Edel >Assignee: Nate Edel >Priority: Major > Labels: BB2015-05-TBR, ipv6 > Attachments: HDFS-8078-HADOOP-17800.001.patch, > HDFS-8078-HADOOP-17800.002.patch, HDFS-8078.10.patch, HDFS-8078.11.patch, > HDFS-8078.12.patch, HDFS-8078.13.patch, HDFS-8078.14.patch, > HDFS-8078.15.patch, HDFS-8078.9.patch, dummy.patch > > > 1st exception, on put: > 15/03/23 18:43:18 WARN hdfs.DFSClient: DataStreamer Exception > java.lang.IllegalArgumentException: Does not contain a valid host:port > authority: 2401:db00:1010:70ba:face:0:8:0:50010 > at org.apache.hadoop.net.NetUtils.createSocketAddr(NetUtils.java:212) > at org.apache.hadoop.net.NetUtils.createSocketAddr(NetUtils.java:164) > at org.apache.hadoop.net.NetUtils.createSocketAddr(NetUtils.java:153) > at > org.apache.hadoop.hdfs.DFSOutputStream.createSocketForPipeline(DFSOutputStream.java:1607) > at > org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.createBlockOutputStream(DFSOutputStream.java:1408) > at > org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.nextBlockOutputStream(DFSOutputStream.java:1361) > at > org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.run(DFSOutputStream.java:588) > Appears to actually stem from code in DataNodeID which assumes it's safe to > append together (ipaddr + ":" + port) -- which is OK for IPv4 and not OK for > IPv6. NetUtils.createSocketAddr( ) assembles a Java URI object, which > requires the format proto://[2401:db00:1010:70ba:face:0:8:0]:50010 > Currently using InetAddress.getByName() to validate IPv6 (guava > InetAddresses.forString has been flaky) but could also use our own parsing. > (From logging this, it seems like a low-enough frequency call that the extra > object creation shouldn't be problematic, and for me the slight risk of > passing in bad input that is not actually an IPv4 or IPv6 address and thus > calling an external DNS lookup is outweighed by getting the address > normalized and avoiding rewriting parsing.) > Alternatively, sun.net.util.IPAddressUtil.isIPv6LiteralAddress() > --- > 2nd exception (on datanode) > 15/04/13 13:18:07 ERROR datanode.DataNode: > dev1903.prn1.facebook.com:50010:DataXceiver error processing unknown > operation src: /2401:db00:20:7013:face:0:7:0:54152 dst: > /2401:db00:11:d010:face:0:2f:0:50010 > java.io.EOFException > at java.io.DataInputStream.readShort(DataInputStream.java:315) > at > org.apache.hadoop.hdfs.protocol.datatransfer.Receiver.readOp(Receiver.java:58) > at > org.apache.hadoop.hdfs.server.datanode.DataXceiver.run(DataXceiver.java:226) > at java.lang.Thread.run(Thread.java:745) > Which also comes as client error "-get: 2401 is not an IP string literal." > This one has existing parsing logic which needs to shift to the last colon > rather than the first. Should also be a tiny bit faster by using lastIndexOf > rather than split. Could alternatively use the techniques above. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-11630) Allow hadoop.sh to bind to ipv6 conditionally
[ https://issues.apache.org/jira/browse/HADOOP-11630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated HADOOP-11630: -- Fix Version/s: HADOOP-17800 Hadoop Flags: Reviewed Resolution: Fixed Status: Resolved (was: Patch Available) Committed to HADOOP-17800 branch.. thanks all.. > Allow hadoop.sh to bind to ipv6 conditionally > - > > Key: HADOOP-11630 > URL: https://issues.apache.org/jira/browse/HADOOP-11630 > Project: Hadoop Common > Issue Type: Sub-task > Components: scripts >Affects Versions: 2.6.0 >Reporter: Elliott Neil Clark >Assignee: Elliott Neil Clark >Priority: Major > Labels: ipv6 > Fix For: HADOOP-17800, HADOOP-11890 > > Attachments: HADOOP-11630-HADOOP-17800.001.patch, > HADOOP-11630-HADOOP-17800.002.patch, HADOOP-11630-HADOOP-17800.003.patch, > HDFS-7834-branch-2-0.patch, HDFS-7834-trunk-0.patch > > > Currently the bash scripts unconditionally add -Djava.net.preferIPv4Stack=true > While this was needed a while ago. IPV6 on java works much better now and > there should be a way to allow it to bind dual stack if needed. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-11630) Allow hadoop.sh to bind to ipv6 conditionally
[ https://issues.apache.org/jira/browse/HADOOP-11630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17384285#comment-17384285 ] Brahma Reddy Battula commented on HADOOP-11630: --- [~brahmareddy] thanks for handling the shell check error and uploading the patch.. +1 on latest. > Allow hadoop.sh to bind to ipv6 conditionally > - > > Key: HADOOP-11630 > URL: https://issues.apache.org/jira/browse/HADOOP-11630 > Project: Hadoop Common > Issue Type: Sub-task > Components: scripts >Affects Versions: 2.6.0 >Reporter: Elliott Neil Clark >Assignee: Elliott Neil Clark >Priority: Major > Labels: ipv6 > Fix For: HADOOP-11890 > > Attachments: HADOOP-11630-HADOOP-17800.001.patch, > HADOOP-11630-HADOOP-17800.002.patch, HADOOP-11630-HADOOP-17800.003.patch, > HDFS-7834-branch-2-0.patch, HDFS-7834-trunk-0.patch > > > Currently the bash scripts unconditionally add -Djava.net.preferIPv4Stack=true > While this was needed a while ago. IPV6 on java works much better now and > there should be a way to allow it to bind dual stack if needed. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-11630) Allow hadoop.sh to bind to ipv6 conditionally
[ https://issues.apache.org/jira/browse/HADOOP-11630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17382104#comment-17382104 ] Brahma Reddy Battula commented on HADOOP-11630: --- [~hemanthboyina] thanks for uploading the patch.. Can we address shell check error which is reported by Jenkins... We can have ternary operator. > Allow hadoop.sh to bind to ipv6 conditionally > - > > Key: HADOOP-11630 > URL: https://issues.apache.org/jira/browse/HADOOP-11630 > Project: Hadoop Common > Issue Type: Sub-task > Components: scripts >Affects Versions: 2.6.0 >Reporter: Elliott Neil Clark >Assignee: Elliott Neil Clark >Priority: Major > Labels: ipv6 > Fix For: HADOOP-11890 > > Attachments: HADOOP-11630-HADOOP-17800.001.patch, > HADOOP-11630-HADOOP-17800.002.patch, HDFS-7834-branch-2-0.patch, > HDFS-7834-trunk-0.patch > > > Currently the bash scripts unconditionally add -Djava.net.preferIPv4Stack=true > While this was needed a while ago. IPV6 on java works much better now and > there should be a way to allow it to bind dual stack if needed. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-11890) Uber-JIRA: Hadoop should support IPv6
[ https://issues.apache.org/jira/browse/HADOOP-11890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17382088#comment-17382088 ] Brahma Reddy Battula commented on HADOOP-11890: --- thanks a lot, we'll go head.. > Uber-JIRA: Hadoop should support IPv6 > - > > Key: HADOOP-11890 > URL: https://issues.apache.org/jira/browse/HADOOP-11890 > Project: Hadoop Common > Issue Type: Improvement > Components: net >Reporter: Nate Edel >Assignee: Nate Edel >Priority: Major > Labels: ipv6 > Attachments: hadoop_2.7.3_ipv6_commits.txt > > > Hadoop currently treats IPv6 as unsupported. Track related smaller issues to > support IPv6. > (Current case here is mainly HBase on HDFS, so any suggestions about other > test cases/workload are really appreciated.) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-11890) Uber-JIRA: Hadoop should support IPv6
[ https://issues.apache.org/jira/browse/HADOOP-11890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17381502#comment-17381502 ] Brahma Reddy Battula commented on HADOOP-11890: --- Agree with you.. My thought was, Don't want to delete existing branch as this is based on the branch-2.7 which might be used for future reference.(Anyway stale branches will be delete at one point of time but I want to keep at least this merged to trunk) And I clone the only parent jira because I want to same subtasks/reference of this jira (don't want to create all the subtasks again) can be used. I will try to update the cloned jira description...If it's not make sense, let me know your thoughts for proceeding further. > Uber-JIRA: Hadoop should support IPv6 > - > > Key: HADOOP-11890 > URL: https://issues.apache.org/jira/browse/HADOOP-11890 > Project: Hadoop Common > Issue Type: Improvement > Components: net >Reporter: Nate Edel >Assignee: Nate Edel >Priority: Major > Labels: ipv6 > Attachments: hadoop_2.7.3_ipv6_commits.txt > > > Hadoop currently treats IPv6 as unsupported. Track related smaller issues to > support IPv6. > (Current case here is mainly HBase on HDFS, so any suggestions about other > test cases/workload are really appreciated.) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-11890) Uber-JIRA: Hadoop should support IPv6
[ https://issues.apache.org/jira/browse/HADOOP-11890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17380834#comment-17380834 ] Brahma Reddy Battula commented on HADOOP-11890: --- Just cloned parent jira to create the branch rest everything will be tracked here itself(To keep this branch till at least this feature will get merged).Not planning to clone other jira's, will just reopen and upload the patches against latest trunk. > Uber-JIRA: Hadoop should support IPv6 > - > > Key: HADOOP-11890 > URL: https://issues.apache.org/jira/browse/HADOOP-11890 > Project: Hadoop Common > Issue Type: Improvement > Components: net >Reporter: Nate Edel >Assignee: Nate Edel >Priority: Major > Labels: ipv6 > Attachments: hadoop_2.7.3_ipv6_commits.txt > > > Hadoop currently treats IPv6 as unsupported. Track related smaller issues to > support IPv6. > (Current case here is mainly HBase on HDFS, so any suggestions about other > test cases/workload are really appreciated.) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-11890) Uber-JIRA: Hadoop should support IPv6
[ https://issues.apache.org/jira/browse/HADOOP-11890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17380303#comment-17380303 ] Brahma Reddy Battula commented on HADOOP-11890: --- [~arp] thanks... Created the HADOOP-17800 branch.. We'll reopen the jira's and commit one by one. > Uber-JIRA: Hadoop should support IPv6 > - > > Key: HADOOP-11890 > URL: https://issues.apache.org/jira/browse/HADOOP-11890 > Project: Hadoop Common > Issue Type: Improvement > Components: net >Reporter: Nate Edel >Assignee: Nate Edel >Priority: Major > Labels: ipv6 > Attachments: hadoop_2.7.3_ipv6_commits.txt > > > Hadoop currently treats IPv6 as unsupported. Track related smaller issues to > support IPv6. > (Current case here is mainly HBase on HDFS, so any suggestions about other > test cases/workload are really appreciated.) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17800) CLONE - Uber-JIRA: Hadoop should support IPv6
[ https://issues.apache.org/jira/browse/HADOOP-17800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated HADOOP-17800: -- Description: Hadoop currently treats IPv6 as unsupported. Track related smaller issues to support IPv6. (Current case here is mainly HBase on HDFS, so any suggestions about other test cases/workload are really appreciated.) Please see [Here | https://issues.apache.org/jira/browse/HADOOP-11890?focusedCommentId=17379845=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17379845] for more details. was: Hadoop currently treats IPv6 as unsupported. Track related smaller issues to support IPv6. (Current case here is mainly HBase on HDFS, so any suggestions about other test cases/workload are really appreciated.) > CLONE - Uber-JIRA: Hadoop should support IPv6 > - > > Key: HADOOP-17800 > URL: https://issues.apache.org/jira/browse/HADOOP-17800 > Project: Hadoop Common > Issue Type: Improvement > Components: net >Reporter: Brahma Reddy Battula >Assignee: Nate Edel >Priority: Major > Labels: ipv6 > > Hadoop currently treats IPv6 as unsupported. Track related smaller issues to > support IPv6. > (Current case here is mainly HBase on HDFS, so any suggestions about other > test cases/workload are really appreciated.) > Please see [Here | > https://issues.apache.org/jira/browse/HADOOP-11890?focusedCommentId=17379845=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17379845] > for more details. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Created] (HADOOP-17800) CLONE - Uber-JIRA: Hadoop should support IPv6
Brahma Reddy Battula created HADOOP-17800: - Summary: CLONE - Uber-JIRA: Hadoop should support IPv6 Key: HADOOP-17800 URL: https://issues.apache.org/jira/browse/HADOOP-17800 Project: Hadoop Common Issue Type: Improvement Components: net Reporter: Brahma Reddy Battula Assignee: Nate Edel Hadoop currently treats IPv6 as unsupported. Track related smaller issues to support IPv6. (Current case here is mainly HBase on HDFS, so any suggestions about other test cases/workload are really appreciated.) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-11890) Uber-JIRA: Hadoop should support IPv6
[ https://issues.apache.org/jira/browse/HADOOP-11890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17379845#comment-17379845 ] Brahma Reddy Battula commented on HADOOP-11890: --- [~arp] thanks for your comment. As [~hemanthboyina] mentioned this is developed on branch-2.7 so there are so many conflicts with latest trunk. Internally We resolved against branch-3.1 and deployed the cluster and tested well ( attached the testcases sheet in HADOOP-17542 ) When we plan for upstream, we feel need to create branch and then go head. (Somehow this was delayed, [~arp] thanks for pitching here and remind us.) We are thinking the following approaches to merge to the trunk. * Create new branch and reopen all the jira's and so that it can run all patches against the trunk. Or * Create a single patch against trunk and run jenkins but this will loose commit history which is might not good . We thinking go with approach 1 . Let me know your thoughts/suggestions on this.. Hope this should be ok for you.. After your reply, we will create the branch (jira) While merging in the discuss thread we keep single patch for review. > Uber-JIRA: Hadoop should support IPv6 > - > > Key: HADOOP-11890 > URL: https://issues.apache.org/jira/browse/HADOOP-11890 > Project: Hadoop Common > Issue Type: Improvement > Components: net >Reporter: Nate Edel >Assignee: Nate Edel >Priority: Major > Labels: ipv6 > Attachments: hadoop_2.7.3_ipv6_commits.txt > > > Hadoop currently treats IPv6 as unsupported. Track related smaller issues to > support IPv6. > (Current case here is mainly HBase on HDFS, so any suggestions about other > test cases/workload are really appreciated.) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17666) Update LICENSE for 3.3.1
[ https://issues.apache.org/jira/browse/HADOOP-17666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17346774#comment-17346774 ] Brahma Reddy Battula commented on HADOOP-17666: --- how about linking all those jira's which upgraded versions ..? Users will aware while backport the issues.. > Update LICENSE for 3.3.1 > > > Key: HADOOP-17666 > URL: https://issues.apache.org/jira/browse/HADOOP-17666 > Project: Hadoop Common > Issue Type: Sub-task >Reporter: Wei-Chiu Chuang >Assignee: Wei-Chiu Chuang >Priority: Blocker > Labels: pull-request-available, release-blocker > Time Spent: 20m > Remaining Estimate: 0h > > Before release, do another round of check for the LICENSE file to make sure > the dependency versions are updated correctly. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17617) Incorrect representation of RESPONSE for Get Key Version in KMS index.md.vm file
[ https://issues.apache.org/jira/browse/HADOOP-17617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated HADOOP-17617: -- Fix Version/s: 3.4.0 3.3.1 Hadoop Flags: Reviewed Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-3.3. [~Sushma_28] thanks for your contribution. > Incorrect representation of RESPONSE for Get Key Version in KMS index.md.vm > file > > > Key: HADOOP-17617 > URL: https://issues.apache.org/jira/browse/HADOOP-17617 > Project: Hadoop Common > Issue Type: Bug >Reporter: Ravuri Sushma sree >Assignee: Ravuri Sushma sree >Priority: Major > Fix For: 3.3.1, 3.4.0 > > Attachments: HADOOP-17617.001.patch, HADOOP-17617.002.patch, > HADOOP-17617.003.patch, KMS_Key_Version_Response_01.png, > KMS_Key_Version_Response_02.png > > > Format of RESPONSE of Get Key Versions in KMS index.md.vm is incorrect > [https://hadoop.apache.org/docs/r3.1.1/hadoop-kms/index.html#Get_Key_Versions] > Attached the outputs of the commands for reference -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17617) Incorrect representation of RESPONSE for Get Key Version in KMS index.md.vm file
[ https://issues.apache.org/jira/browse/HADOOP-17617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17316384#comment-17316384 ] Brahma Reddy Battula commented on HADOOP-17617: --- Lgtm. thanks for updating the patch. > Incorrect representation of RESPONSE for Get Key Version in KMS index.md.vm > file > > > Key: HADOOP-17617 > URL: https://issues.apache.org/jira/browse/HADOOP-17617 > Project: Hadoop Common > Issue Type: Bug >Reporter: Ravuri Sushma sree >Assignee: Ravuri Sushma sree >Priority: Major > Attachments: HADOOP-17617.001.patch, HADOOP-17617.002.patch, > HADOOP-17617.003.patch, KMS_Key_Version_Response_01.png, > KMS_Key_Version_Response_02.png > > > Format of RESPONSE of Get Key Versions in KMS index.md.vm is incorrect > [https://hadoop.apache.org/docs/r3.1.1/hadoop-kms/index.html#Get_Key_Versions] > Attached the outputs of the commands for reference -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17617) Incorrect representation of RESPONSE for Get Key Version in KMS index.md.vm file
[
https://issues.apache.org/jira/browse/HADOOP-17617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17316239#comment-17316239
]
Brahma Reddy Battula commented on HADOOP-17617:
---
[~Sushma_28] thanks for uploading which will be clear for this issue.
One minor nit: Sorry I missed before.
can you change like following..?
|"versionName" : "version"| *To* |"versionName" :
"{color:red}<{color}version{color:red}>{color}",|
> Incorrect representation of RESPONSE for Get Key Version in KMS index.md.vm
> file
>
>
> Key: HADOOP-17617
> URL: https://issues.apache.org/jira/browse/HADOOP-17617
> Project: Hadoop Common
> Issue Type: Bug
>Reporter: Ravuri Sushma sree
>Assignee: Ravuri Sushma sree
>Priority: Major
> Attachments: HADOOP-17617.001.patch, HADOOP-17617.002.patch,
> KMS_Key_Version_Response_01.png, KMS_Key_Version_Response_02.png
>
>
> Format of RESPONSE of Get Key Versions in KMS index.md.vm is incorrect
> [https://hadoop.apache.org/docs/r3.1.1/hadoop-kms/index.html#Get_Key_Versions]
> Attached the outputs of the commands for reference
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17587) Kinit with keytab should not display the keytab file's full path in any logs
[ https://issues.apache.org/jira/browse/HADOOP-17587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated HADOOP-17587: -- Fix Version/s: 3.4.0 3.3.1 Hadoop Flags: Reviewed Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-3.3. [~Sushma_28] thanks for contribution. > Kinit with keytab should not display the keytab file's full path in any logs > > > Key: HADOOP-17587 > URL: https://issues.apache.org/jira/browse/HADOOP-17587 > Project: Hadoop Common > Issue Type: Bug >Reporter: Ravuri Sushma sree >Assignee: Ravuri Sushma sree >Priority: Major > Fix For: 3.3.1, 3.4.0 > > Attachments: HADOOP-17587.001.patch, HADOOP-17587.002.patch > > > The keytab is sensitive information, and the full path should not be printed > in the log -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17610) DelegationTokenAuthenticator prints token information
[ https://issues.apache.org/jira/browse/HADOOP-17610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated HADOOP-17610: -- Fix Version/s: 3.4.0 3.3.1 Hadoop Flags: Reviewed Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-3.3.. [~Sushma_28] thanks for contribution. > DelegationTokenAuthenticator prints token information > - > > Key: HADOOP-17610 > URL: https://issues.apache.org/jira/browse/HADOOP-17610 > Project: Hadoop Common > Issue Type: Bug >Reporter: Ravuri Sushma sree >Assignee: Ravuri Sushma sree >Priority: Major > Fix For: 3.3.1, 3.4.0 > > Attachments: HADOOP-17610.patch > > > Resource Manager logs print token information , as this is sensitive > information it must be exempted from being printed -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17587) Kinit with keytab should not display the keytab file's full path in any logs
[ https://issues.apache.org/jira/browse/HADOOP-17587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313306#comment-17313306 ] Brahma Reddy Battula commented on HADOOP-17587: --- [~Sushma_28] thanks for reporting and uploading the patch.. Patch lgtm, as this is sensitive info can be avoided logging. > Kinit with keytab should not display the keytab file's full path in any logs > > > Key: HADOOP-17587 > URL: https://issues.apache.org/jira/browse/HADOOP-17587 > Project: Hadoop Common > Issue Type: Bug >Reporter: Ravuri Sushma sree >Assignee: Ravuri Sushma sree >Priority: Major > Attachments: HADOOP-17587.001.patch, HADOOP-17587.002.patch > > > The keytab is sensitive information, and the full path should not be printed > in the log -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17610) DelegationTokenAuthenticator prints token information
[ https://issues.apache.org/jira/browse/HADOOP-17610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313304#comment-17313304 ] Brahma Reddy Battula commented on HADOOP-17610: --- [~Sushma_28] thanks for reporting this Jira and uploading the patch. As this is sensitive information can be avoided. Patch lgtm.. Looks jenkins error not relevant. > DelegationTokenAuthenticator prints token information > - > > Key: HADOOP-17610 > URL: https://issues.apache.org/jira/browse/HADOOP-17610 > Project: Hadoop Common > Issue Type: Bug >Reporter: Ravuri Sushma sree >Assignee: Ravuri Sushma sree >Priority: Major > Attachments: HADOOP-17610.patch > > > Resource Manager logs print token information , as this is sensitive > information it must be exempted from being printed -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17617) Incorrect representation of RESPONSE for Get Key Version in KMS index.md.vm file
[ https://issues.apache.org/jira/browse/HADOOP-17617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313302#comment-17313302 ] Brahma Reddy Battula commented on HADOOP-17617: --- [~Sushma_28] can you keep the command output in this jira..? > Incorrect representation of RESPONSE for Get Key Version in KMS index.md.vm > file > > > Key: HADOOP-17617 > URL: https://issues.apache.org/jira/browse/HADOOP-17617 > Project: Hadoop Common > Issue Type: Bug >Reporter: Ravuri Sushma sree >Assignee: Ravuri Sushma sree >Priority: Major > Attachments: HADOOP-17617.001.patch, HADOOP-17617.002.patch > > > Format of RESPONSE of Get Key Versions in KMS index.md.vm is incorrect > https://hadoop.apache.org/docs/r3.1.1/hadoop-kms/index.html#Get_Key_Versions -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17588) CryptoInputStream#close() should be syncronized
[ https://issues.apache.org/jira/browse/HADOOP-17588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17312111#comment-17312111 ] Brahma Reddy Battula commented on HADOOP-17588: --- [~prasad-acit] patch lgtm. > CryptoInputStream#close() should be syncronized > --- > > Key: HADOOP-17588 > URL: https://issues.apache.org/jira/browse/HADOOP-17588 > Project: Hadoop Common > Issue Type: Bug >Reporter: Renukaprasad C >Assignee: Renukaprasad C >Priority: Major > Attachments: HADOOP-17588.001.patch, image-2021-03-13-23-56-18-865.png > > > org.apache.hadoop.crypto.CryptoInputStream.close() - when 2 threads try to > close the stream second thread, fails with error. > This operation should be synchronized to avoid multiple threads to perform > the close operation concurrently. > !image-2021-03-13-23-56-18-865.png|thumbnail! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17593) hadoop-huaweicloud and hadoop-cloud-storage to remove log4j as transitive dependency
[ https://issues.apache.org/jira/browse/HADOOP-17593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17311528#comment-17311528 ] Brahma Reddy Battula commented on HADOOP-17593: --- [~Rigenyi] thanks for uploading the patch. Patch lgtm. will wait for [~ste...@apache.org] comment on this. > hadoop-huaweicloud and hadoop-cloud-storage to remove log4j as transitive > dependency > > > Key: HADOOP-17593 > URL: https://issues.apache.org/jira/browse/HADOOP-17593 > Project: Hadoop Common > Issue Type: Bug > Components: build >Affects Versions: 3.3.1, 3.4.0 >Reporter: Steve Loughran >Assignee: lixianwei >Priority: Major > Attachments: HADOOP-17593.001.patch > > > Dependencies of hadoop-cloud-storage show that hadoop-huaweicloud is pulling > in logj4. > it should not/must not, at least, not if the huaweicloud can live without it. > * A version of log4j 2.,2 on the CP is only going to complicate lives > * once we can move onto it ourselves we need to be in control of versions > [INFO] \- org.apache.hadoop:hadoop-huaweicloud:jar:3.4.0-SNAPSHOT:compile > [INFO]\- com.huaweicloud:esdk-obs-java:jar:3.20.4.2:compile > [INFO] +- com.jamesmurty.utils:java-xmlbuilder:jar:1.2:compile > [INFO] +- com.squareup.okhttp3:okhttp:jar:3.14.2:compile > [INFO] +- org.apache.logging.log4j:log4j-core:jar:2.12.0:compile > [INFO] \- org.apache.logging.log4j:log4j-api:jar:2.12.0:compile -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Assigned] (HADOOP-17593) hadoop-huaweicloud and hadoop-cloud-storage to remove log4j as transitive dependency
[ https://issues.apache.org/jira/browse/HADOOP-17593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula reassigned HADOOP-17593: - Assignee: lixianwei > hadoop-huaweicloud and hadoop-cloud-storage to remove log4j as transitive > dependency > > > Key: HADOOP-17593 > URL: https://issues.apache.org/jira/browse/HADOOP-17593 > Project: Hadoop Common > Issue Type: Bug > Components: build >Affects Versions: 3.3.1, 3.4.0 >Reporter: Steve Loughran >Assignee: lixianwei >Priority: Major > > Dependencies of hadoop-cloud-storage show that hadoop-huaweicloud is pulling > in logj4. > it should not/must not, at least, not if the huaweicloud can live without it. > * A version of log4j 2.,2 on the CP is only going to complicate lives > * once we can move onto it ourselves we need to be in control of versions > [INFO] \- org.apache.hadoop:hadoop-huaweicloud:jar:3.4.0-SNAPSHOT:compile > [INFO]\- com.huaweicloud:esdk-obs-java:jar:3.20.4.2:compile > [INFO] +- com.jamesmurty.utils:java-xmlbuilder:jar:1.2:compile > [INFO] +- com.squareup.okhttp3:okhttp:jar:3.14.2:compile > [INFO] +- org.apache.logging.log4j:log4j-core:jar:2.12.0:compile > [INFO] \- org.apache.logging.log4j:log4j-api:jar:2.12.0:compile -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17593) hadoop-huaweicloud and hadoop-cloud-storage to remove log4j as transitive dependency
[ https://issues.apache.org/jira/browse/HADOOP-17593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17310551#comment-17310551 ] Brahma Reddy Battula commented on HADOOP-17593: --- Hi [~Rigenyi] , I added you as contributor to hadoop common project, now you can upload the patch. welcome to onboard. > hadoop-huaweicloud and hadoop-cloud-storage to remove log4j as transitive > dependency > > > Key: HADOOP-17593 > URL: https://issues.apache.org/jira/browse/HADOOP-17593 > Project: Hadoop Common > Issue Type: Bug > Components: build >Affects Versions: 3.3.1, 3.4.0 >Reporter: Steve Loughran >Priority: Major > > Dependencies of hadoop-cloud-storage show that hadoop-huaweicloud is pulling > in logj4. > it should not/must not, at least, not if the huaweicloud can live without it. > * A version of log4j 2.,2 on the CP is only going to complicate lives > * once we can move onto it ourselves we need to be in control of versions > [INFO] \- org.apache.hadoop:hadoop-huaweicloud:jar:3.4.0-SNAPSHOT:compile > [INFO]\- com.huaweicloud:esdk-obs-java:jar:3.20.4.2:compile > [INFO] +- com.jamesmurty.utils:java-xmlbuilder:jar:1.2:compile > [INFO] +- com.squareup.okhttp3:okhttp:jar:3.14.2:compile > [INFO] +- org.apache.logging.log4j:log4j-core:jar:2.12.0:compile > [INFO] \- org.apache.logging.log4j:log4j-api:jar:2.12.0:compile -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17579) refresh freatures description of HuaweiCloud OBS Adapter for Hadoop Support
[ https://issues.apache.org/jira/browse/HADOOP-17579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17300072#comment-17300072 ] Brahma Reddy Battula commented on HADOOP-17579: --- looks this is duplicate to HADOOP-17580..? > refresh freatures description of HuaweiCloud OBS Adapter for Hadoop Support > --- > > Key: HADOOP-17579 > URL: https://issues.apache.org/jira/browse/HADOOP-17579 > Project: Hadoop Common > Issue Type: Improvement >Affects Versions: 3.3.0 >Reporter: wenzhen >Priority: Minor > Fix For: 3.3.0 > > > Refresh freatures description of HuaweiCloud OBS Adapter for Hadoop Support, > such as : > rename, Append , hflush support. > link : > hadoop/hadoop-cloud-storage-project/hadoop-huaweicloud/src/site/markdown/index.md > Features > Present a hierarchical HDFS file system by implementing the standard Hadoop > FileSystem interface. > In hadoop, Read and write data stored in a HuaweiCloud OBS bucket. > Can act as a source of data in a MapReduce job, or a sink. > Support multipart upload for a large file. > Reference file system paths using URLs using the obs scheme. > Uses HuaweiCloud OBS’s Java SDK with support for latest OBS features and > authentication schemes. > For OBS 'Parallel file system bucket'(Posix), support rename with atomic > semantics, Append, hflush > For OBS 'Parallel file system bucket'(Posix), Provide trash mechanism and > quickly delete, which using rename and lifecircle of OBS bucket. > Tested for scale. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17543) HDFS Put was failed with IPV6 cluster
[ https://issues.apache.org/jira/browse/HADOOP-17543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated HADOOP-17543: -- Parent: HADOOP-11890 Issue Type: Sub-task (was: Improvement) > HDFS Put was failed with IPV6 cluster > -- > > Key: HADOOP-17543 > URL: https://issues.apache.org/jira/browse/HADOOP-17543 > Project: Hadoop Common > Issue Type: Sub-task >Affects Versions: 3.1.1 >Reporter: ANANDA G B >Priority: Minor > Labels: ipv6 > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Moved] (HADOOP-17543) HDFS Put was failed with IPV6 cluster
[ https://issues.apache.org/jira/browse/HADOOP-17543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula moved HDFS-15852 to HADOOP-17543: -- Component/s: (was: hdfs) Key: HADOOP-17543 (was: HDFS-15852) Target Version/s: 3.3.1 (was: 3.3.1) Affects Version/s: (was: 3.1.1) 3.1.1 Project: Hadoop Common (was: Hadoop HDFS) > HDFS Put was failed with IPV6 cluster > -- > > Key: HADOOP-17543 > URL: https://issues.apache.org/jira/browse/HADOOP-17543 > Project: Hadoop Common > Issue Type: Improvement >Affects Versions: 3.1.1 >Reporter: ANANDA G B >Priority: Minor > Labels: ipv6 > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17542) Avoid unsafe split and append on fields that might be IPv6 literals
[ https://issues.apache.org/jira/browse/HADOOP-17542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated HADOOP-17542: -- Parent: HADOOP-11890 Issue Type: Sub-task (was: Bug) > Avoid unsafe split and append on fields that might be IPv6 literals > --- > > Key: HADOOP-17542 > URL: https://issues.apache.org/jira/browse/HADOOP-17542 > Project: Hadoop Common > Issue Type: Sub-task >Affects Versions: 3.1.1 >Reporter: ANANDA G B >Priority: Minor > Labels: ipv6 > Attachments: HDFS-15851_001.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Moved] (HADOOP-17542) Avoid unsafe split and append on fields that might be IPv6 literals
[ https://issues.apache.org/jira/browse/HADOOP-17542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula moved HDFS-15851 to HADOOP-17542: -- Component/s: (was: hdfs) Fix Version/s: (was: 3.3.1) Key: HADOOP-17542 (was: HDFS-15851) Target Version/s: 3.3.1 (was: 3.3.1) Affects Version/s: (was: 3.1.1) 3.1.1 Issue Type: Bug (was: Improvement) Project: Hadoop Common (was: Hadoop HDFS) > Avoid unsafe split and append on fields that might be IPv6 literals > --- > > Key: HADOOP-17542 > URL: https://issues.apache.org/jira/browse/HADOOP-17542 > Project: Hadoop Common > Issue Type: Bug >Affects Versions: 3.1.1 >Reporter: ANANDA G B >Priority: Minor > Labels: ipv6 > Attachments: HDFS-15851_001.patch > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Commented] (HADOOP-17510) Hadoop prints sensitive Cookie information.
[
https://issues.apache.org/jira/browse/HADOOP-17510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17286549#comment-17286549
]
Brahma Reddy Battula commented on HADOOP-17510:
---
[~prasad-acit] thanks for reporting.. Sensitive information can be deleted..
Patch LGTM.
> Hadoop prints sensitive Cookie information.
> ---
>
> Key: HADOOP-17510
> URL: https://issues.apache.org/jira/browse/HADOOP-17510
> Project: Hadoop Common
> Issue Type: Bug
>Affects Versions: 3.3.0
>Reporter: Renukaprasad C
>Priority: Major
> Labels: pull-request-available
> Time Spent: 50m
> Remaining Estimate: 0h
>
> org.apache.hadoop.security.authentication.client.AuthenticatedURL.AuthCookieHandler#setAuthCookie
> - prints cookie information in log. Any sensitive infomation in Cookies will
> be logged, which needs to be avaided.
> LOG.trace("Setting token value to {} ({})", authCookie, oldCookie);
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
