[jira] [Resolved] (HADOOP-18365) Updated addresses are still accessed using the old IP address

2022-08-22 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-18365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stack resolved HADOOP-18365. Hadoop Flags: Reviewed Resolution: Fixed PR merged to branch-3.3 and to trunk.

[jira] [Resolved] (HADOOP-18228) Update hadoop-vote to use HADOOP_RC_VERSION dir

2022-05-16 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-18228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stack resolved HADOOP-18228. Fix Version/s: 3.4.0 Hadoop Flags: Reviewed Resolution: Fixed > Update

[jira] [Updated] (HADOOP-17725) Improve error message for token providers in ABFS

2022-03-02 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-17725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stack updated HADOOP-17725: --- Fix Version/s: 3.3.3 (was: 3.3.2) > Improve error message for token

[jira] [Commented] (HADOOP-17665) Ignore missing keystore configuration in reloading mechanism

2021-05-17 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-17665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17345908#comment-17345908 ] Michael Stack commented on HADOOP-17665: Thank you [~weichiu] > Ignore missing keystore

[jira] [Commented] (HADOOP-16524) Automatic keystore reloading for HttpServer2

2021-05-10 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17342149#comment-17342149 ] Michael Stack commented on HADOOP-16524: I merged the sub-task PR to trunk and branch-3.3.

[jira] [Commented] (HADOOP-17665) Ignore missing keystore configuration in reloading mechanism

2021-05-10 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-17665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17342141#comment-17342141 ] Michael Stack commented on HADOOP-17665: Merged to trunk and branch-3.3. It doesn't apply to

[jira] [Commented] (HADOOP-16524) Automatic keystore reloading for HttpServer2

2021-05-04 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339100#comment-17339100 ] Michael Stack commented on HADOOP-16524: Thanks [~borislav.iordanov]. Is that ok by you

[jira] [Commented] (HADOOP-16524) Automatic keystore reloading for HttpServer2

2021-05-04 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339022#comment-17339022 ] Michael Stack commented on HADOOP-16524: Thanks for following up [~ayushtkn]. Lets see if Boris

[jira] [Commented] (HADOOP-16524) Automatic keystore reloading for HttpServer2

2021-04-21 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17326692#comment-17326692 ] Michael Stack commented on HADOOP-16524: bq. What I could do is create a PR with a more helpful

[jira] [Commented] (HADOOP-16524) Automatic keystore reloading for HttpServer2

2021-04-13 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17320580#comment-17320580 ] Michael Stack commented on HADOOP-16524: ACK [~ayushtkn] Thanks for ping. Looking... >

[jira] [Resolved] (HADOOP-16524) Automatic keystore reloading for HttpServer2

2021-03-31 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stack resolved HADOOP-16524. Resolution: Fixed Resolving again. Thanks for the feature [~borislav.iordanov] contrib.

[jira] [Commented] (HADOOP-16524) Automatic keystore reloading for HttpServer2

2021-03-31 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17312594#comment-17312594 ] Michael Stack commented on HADOOP-16524: Pushed new PR that fixes yarn issue to branch-3.3 and

[jira] [Reopened] (HADOOP-16524) Automatic keystore reloading for HttpServer2

2021-01-11 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stack reopened HADOOP-16524: Reopening to revert change until fix failing yarn test. > Automatic keystore reloading for

[jira] [Commented] (HADOOP-16524) Automatic keystore reloading for HttpServer2

2021-01-11 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17262785#comment-17262785 ] Michael Stack commented on HADOOP-16524: Reverted from trunk and branch-3.3. > Automatic

[jira] [Commented] (HADOOP-16524) Automatic keystore reloading for HttpServer2

2021-01-11 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17262777#comment-17262777 ] Michael Stack commented on HADOOP-16524: Sorry about that. Thanks for the ping. I applied

[jira] [Updated] (HADOOP-16524) Automatic keystore reloading for HttpServer2

2021-01-08 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stack updated HADOOP-16524: --- Fix Version/s: 3.4.0 3.3.1 Hadoop Flags: Reviewed Release

[jira] [Commented] (HADOOP-16524) Automatic keystore reloading for HttpServer2

2021-01-08 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17261467#comment-17261467 ] Michael Stack commented on HADOOP-16524: Merged to trunk. Put up #2609 backport to branch-3.3.

[jira] [Commented] (HADOOP-16524) Automatic keystore reloading for HttpServer2

2020-12-09 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246968#comment-17246968 ] Michael Stack commented on HADOOP-16524: Attached PR LGTM. Would appreciate someone else taking

[jira] [Commented] (HADOOP-17288) Use shaded guava from thirdparty

2020-11-13 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-17288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17231687#comment-17231687 ] Michael Stack commented on HADOOP-17288: +1 on backport. Will ease move to 3.3.x\+ > Use

[jira] [Commented] (HADOOP-17288) Use shaded guava from thirdparty

2020-10-07 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-17288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17209740#comment-17209740 ] Michael Stack commented on HADOOP-17288: [~ayushtkn] talking out loud, 3.2.1 and 3.3.0 shipped

[jira] [Commented] (HADOOP-17288) Use shaded guava from thirdparty

2020-10-05 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-17288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17208255#comment-17208255 ] Michael Stack commented on HADOOP-17288: Looking good [~ayushtkn] . You thinking that this

[jira] [Commented] (HADOOP-17288) Use shaded guava from thirdparty

2020-10-01 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-17288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17205644#comment-17205644 ] Michael Stack commented on HADOOP-17288: {quote}Ideally if the downstream has to upgrade guava,

[jira] [Updated] (HADOOP-17288) Use shaded guava from thirdparty

2020-10-01 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-17288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stack updated HADOOP-17288: --- Fix Version/s: 3.4.0 > Use shaded guava from thirdparty >

[jira] [Commented] (HADOOP-17288) Use shaded guava from thirdparty

2020-10-01 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-17288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17205329#comment-17205329 ] Michael Stack commented on HADOOP-17288: {quote}but guava as of now would be still packaged as

[jira] [Commented] (HADOOP-17288) Use shaded guava from thirdparty

2020-09-30 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-17288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17205259#comment-17205259 ] Michael Stack commented on HADOOP-17288: [~ayushtkn] What is the approach here (big patch,

[jira] [Commented] (HADOOP-17254) Upgrade hbase to 1.2.6.1 on branch-2.10

2020-09-09 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-17254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17193302#comment-17193302 ] Michael Stack commented on HADOOP-17254: Yeah, upgrade if you can... 1.2.x, 1.3.x are EOL'd. >

[jira] [Resolved] (HADOOP-16598) Backport "HADOOP-16558 [COMMON+HDFS] use protobuf-maven-plugin to generate protobuf classes" to all active branches

2019-11-01 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stack resolved HADOOP-16598. Resolution: Fixed Reclosing after fixing branch-2 and branch-2.9 commits (revert and

[jira] [Reopened] (HADOOP-16598) Backport "HADOOP-16558 [COMMON+HDFS] use protobuf-maven-plugin to generate protobuf classes" to all active branches

2019-11-01 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stack reopened HADOOP-16598: Thanks for checking. Reopening while I fix. > Backport "HADOOP-16558 [COMMON+HDFS] use

[jira] [Updated] (HADOOP-16598) Backport "HADOOP-16558 [COMMON+HDFS] use protobuf-maven-plugin to generate protobuf classes" to all active branches

2019-10-31 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stack updated HADOOP-16598: --- Fix Version/s: 2.11.0 2.10.1 3.2.2

[jira] [Commented] (HADOOP-16598) Backport "HADOOP-16558 [COMMON+HDFS] use protobuf-maven-plugin to generate protobuf classes" to all active branches

2019-10-17 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16954173#comment-16954173 ] Michael Stack commented on HADOOP-16598: I tried the 3.2 patch by applying it, cleaning the

[jira] [Updated] (HADOOP-16600) StagingTestBase uses methods not available in Mockito 1.8.5 in branch-3.1

2019-10-17 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stack updated HADOOP-16600: --- Hadoop Flags: Reviewed Resolution: Fixed Status: Resolved (was: Patch

[jira] [Commented] (HADOOP-16600) StagingTestBase uses methods not available in Mockito 1.8.5 in branch-3.1

2019-10-12 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16950207#comment-16950207 ] Michael Stack commented on HADOOP-16600: +1 > StagingTestBase uses methods not available in

[jira] [Updated] (HADOOP-16598) Backport "HADOOP-16558 [COMMON+HDFS] use protobuf-maven-plugin to generate protobuf classes" to all active branches

2019-10-03 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stack updated HADOOP-16598: --- Attachment: HADOOP-16598-branch-2.9-v1.patch > Backport "HADOOP-16558 [COMMON+HDFS] use

[jira] [Commented] (HADOOP-16598) Backport "HADOOP-16558 [COMMON+HDFS] use protobuf-maven-plugin to generate protobuf classes" to all active branches

2019-10-03 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16944166#comment-16944166 ] Michael Stack commented on HADOOP-16598: Retry. Was going to commit this tomorrow unless

[jira] [Updated] (HADOOP-16598) Backport "HADOOP-16558 [COMMON+HDFS] use protobuf-maven-plugin to generate protobuf classes" to all active branches

2019-10-03 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stack updated HADOOP-16598: --- Attachment: HADOOP-16598-branch-2-v1.patch > Backport "HADOOP-16558 [COMMON+HDFS] use

[jira] [Commented] (HADOOP-13363) Upgrade protobuf from 2.5.0 to something newer

2019-09-30 Thread Michael Stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-13363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16941228#comment-16941228 ] Michael Stack commented on HADOOP-13363: bq. If we are passing protobuf types around, either as

[jira] [Commented] (HADOOP-13363) Upgrade protobuf from 2.5.0 to something newer

2019-09-12 Thread stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-13363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928795#comment-16928795 ] stack commented on HADOOP-13363: One thought, just use the hbase-thirdparty jar? Shaded protobuf,

[jira] [Commented] (HADOOP-13363) Upgrade protobuf from 2.5.0 to something newer

2019-09-12 Thread stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-13363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928784#comment-16928784 ] stack commented on HADOOP-13363: On your #1 and #2 choices above, #1 works for us. Cost is negligible

[jira] [Commented] (HADOOP-13363) Upgrade protobuf from 2.5.0 to something newer

2019-09-06 Thread stack (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-13363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16924511#comment-16924511 ] stack commented on HADOOP-13363: Perhaps this pom helps?

[jira] [Commented] (HADOOP-15566) Support Opentracing

2019-05-07 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835080#comment-16835080 ] stack commented on HADOOP-15566: Thanks for the pointer [~bogdandrutu] > Support Opentracing >

[jira] [Commented] (HADOOP-15566) Remove HTrace support

2018-08-15 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16581273#comment-16581273 ] stack commented on HADOOP-15566: [~elek] Thanks. Or we could just strip htrace. This would remove any

[jira] [Commented] (HADOOP-15566) Remove HTrace support

2018-07-30 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16562619#comment-16562619 ] stack commented on HADOOP-15566: bq. I just think we're going to be hard-pressed to make an informed

[jira] [Commented] (HADOOP-15566) Remove HTrace support

2018-07-28 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16561007#comment-16561007 ] stack commented on HADOOP-15566: Thanks for the input [~michaelsembwever]. bq. as the effort is

[jira] [Commented] (HADOOP-15566) Remove HTrace support

2018-07-23 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-15566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16553144#comment-16553144 ] stack commented on HADOOP-15566: For me, the hard part is not which tracing lib to use -- if a tracing

[jira] [Commented] (HADOOP-13866) Upgrade netty-all to 4.1.1.Final

2017-09-23 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-13866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177943#comment-16177943 ] stack commented on HADOOP-13866: This issue is no longer relevant. HBase shades its netty dependency.

[jira] [Commented] (HADOOP-13363) Upgrade protobuf from 2.5.0 to something newer

2017-09-14 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-13363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16167304#comment-16167304 ] stack commented on HADOOP-13363: I'd presume upgrade but run in pb2 mode, the default. That has been

[jira] [Commented] (HADOOP-14284) Shade Guava everywhere

2017-08-16 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16129662#comment-16129662 ] stack commented on HADOOP-14284: The particular example you cite goes away if hadoop embeds hbase2 since

[jira] [Commented] (HADOOP-14284) Shade Guava everywhere

2017-08-14 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16126355#comment-16126355 ] stack commented on HADOOP-14284: bq. Does HBase shade across all code base, instead of just in client

[jira] [Commented] (HADOOP-14284) Shade Guava everywhere

2017-08-14 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16126187#comment-16126187 ] stack commented on HADOOP-14284: If it helps, here is what was done over in hbase to make it so we could

[jira] [Commented] (HADOOP-14284) Shade Guava everywhere

2017-05-08 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16001566#comment-16001566 ] stack commented on HADOOP-14284: bq. ...get rid of it This doesn't seem right either mighty [~djp].

[jira] [Commented] (HADOOP-14284) Shade Guava everywhere

2017-05-04 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15996980#comment-15996980 ] stack commented on HADOOP-14284: bq. However, I found one problem in this approach: shaded

[jira] [Commented] (HADOOP-14284) Shade Guava everywhere

2017-04-14 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-14284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15969481#comment-15969481 ] stack commented on HADOOP-14284: HBase cheats. It has an unofficial pre-build step, the product of which

[jira] [Commented] (HADOOP-13363) Upgrade protobuf from 2.5.0 to something newer

2017-04-06 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-13363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958358#comment-15958358 ] stack commented on HADOOP-13363: You can ask shading to only bundle required classes which should cut

[jira] [Commented] (HADOOP-13363) Upgrade protobuf from 2.5.0 to something newer

2017-04-05 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-13363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958253#comment-15958253 ] stack commented on HADOOP-13363: [~kihwal] Good point. What we thinking for a shading approach?

[jira] [Commented] (HADOOP-13363) Upgrade protobuf from 2.5.0 to something newer

2017-03-28 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-13363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15946364#comment-15946364 ] stack commented on HADOOP-13363: [~ozawa] Yes sir. Default mode is proto2. You have to explicitly ask

[jira] [Commented] (HADOOP-13363) Upgrade protobuf from 2.5.0 to something newer

2017-03-27 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-13363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15944328#comment-15944328 ] stack commented on HADOOP-13363: HBase uses pb3 internally because you can avoid having to copy all

[jira] [Commented] (HADOOP-13866) Upgrade netty-all to 4.1.1.Final

2017-02-08 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-13866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15859123#comment-15859123 ] stack commented on HADOOP-13866: +1 for master branch then (after update to latest 4.1.x). We'll need to

[jira] [Commented] (HADOOP-13866) Upgrade netty-all to 4.1.1.Final

2017-02-07 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-13866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15856940#comment-15856940 ] stack commented on HADOOP-13866: Latest netty release on 4.1 is 4.1.8, not 4.1.1. Might want to go to

[jira] [Commented] (HADOOP-13866) Upgrade netty-all to 4.1.1.Final

2017-02-03 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-13866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15851878#comment-15851878 ] stack commented on HADOOP-13866: I tried the patch here against the hadoop 2.7 branch and it fixed my

[jira] [Commented] (HADOOP-13433) Race in UGI.reloginFromKeytab

2017-01-26 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-13433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15840614#comment-15840614 ] stack commented on HADOOP-13433: Thanks [~steve_l] for taking care of the commit. > Race in

[jira] [Commented] (HADOOP-13433) Race in UGI.reloginFromKeytab

2017-01-24 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-13433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836380#comment-15836380 ] stack commented on HADOOP-13433: So, patch is only suited to branch-3 [~Apache9]? Worth a version w/ UTs

[jira] [Commented] (HADOOP-13433) Race in UGI.reloginFromKeytab

2017-01-09 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-13433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15812310#comment-15812310 ] stack commented on HADOOP-13433: Should the test case be integrated into the patch [~Apache9]? Have you

[jira] [Commented] (HADOOP-13363) Upgrade protobuf from 2.5.0 to something newer

2016-10-18 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-13363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15587093#comment-15587093 ] stack commented on HADOOP-13363: Did a ML discussion happen? pb3.1.0 is out. It runs in a 2.5.0

[jira] [Commented] (HADOOP-12910) Add new FileSystem API to support asynchronous method calls

2016-06-09 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323884#comment-15323884 ] stack commented on HADOOP-12910: bq. Chaining/callbacks are nonessential in the sense that they can

[jira] [Commented] (HADOOP-12910) Add new FileSystem API to support asynchronous method calls

2016-06-09 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15323118#comment-15323118 ] stack commented on HADOOP-12910: bq. No, they are the same API. Branch-2 is a simplified version of

[jira] [Commented] (HADOOP-12910) Add new FileSystem API to support asynchronous method calls

2016-06-07 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15318747#comment-15318747 ] stack commented on HADOOP-12910: Why the insistence on doing the async twice? Once for branch-2 and then

[jira] [Commented] (HADOOP-12910) Add new FileSystem API to support asynchronous method calls

2016-06-06 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15317848#comment-15317848 ] stack commented on HADOOP-12910: bq. For branch-2, There are two possible ways to use Deferred (or

[jira] [Commented] (HADOOP-12910) Add new FileSystem API to support asynchronous method calls

2016-06-03 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15314599#comment-15314599 ] stack commented on HADOOP-12910: Back now [~cnauroth] bq. ...whereas the scope of this issue has

[jira] [Commented] (HADOOP-12910) Add new FileSystem API to support asynchronous method calls

2016-05-29 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15306068#comment-15306068 ] stack commented on HADOOP-12910: OpenTSDB is LGPL but Deferred is not. It looks to be BSD. A jar that

[jira] [Commented] (HADOOP-12910) Add new FileSystem API to support asynchronous method calls

2016-05-27 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15304159#comment-15304159 ] stack commented on HADOOP-12910: Copy/Paste of Deferred would work. It does callback, has a respectable

[jira] [Commented] (HADOOP-12910) Add new FileSystem API to support asynchronous method calls

2016-05-26 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303503#comment-15303503 ] stack commented on HADOOP-12910: bq. Why making the entire async feature unavailable in branch 2? I'd

[jira] [Commented] (HADOOP-12910) Add new FileSystem API to support asynchronous method calls

2016-05-26 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302854#comment-15302854 ] stack commented on HADOOP-12910: Good suggestion. We'll be back. > Add new FileSystem API to support

[jira] [Commented] (HADOOP-12910) Add new FileSystem API to support asynchronous method calls

2016-05-25 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-12910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15301094#comment-15301094 ] stack commented on HADOOP-12910: The patch here converts one method only? Is the intent to do all

[jira] [Commented] (HADOOP-12447) Clean up some htrace integration issues

2015-09-29 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-12447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14935080#comment-14935080 ] stack commented on HADOOP-12447: +1 from me. Cleans up doc so it refers to 4.0.1 htrace API. Fixes

[jira] [Commented] (HADOOP-12403) Enable multiple writes in flight for HBase WAL writing backed by WASB

2015-09-11 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-12403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14741083#comment-14741083 ] stack commented on HADOOP-12403: bq. The latest HBase WAL write model (HBASE-8755) uses multiple

[jira] [Commented] (HADOOP-12201) Add tracing to FileSystem#createFileSystem and Globber#glob

2015-07-08 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-12201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14619310#comment-14619310 ] stack commented on HADOOP-12201: +1 I like the pretty picture [~cmccabe] Add tracing

[jira] [Commented] (HADOOP-12171) Shorten overly-long htrace span names for server

2015-07-01 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-12171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14610828#comment-14610828 ] stack commented on HADOOP-12171: fullClassNameToTraceString looks like utility that

[jira] [Commented] (HADOOP-12171) Shorten overly-long htrace span names for server

2015-07-01 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-12171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14611192#comment-14611192 ] stack commented on HADOOP-12171: +1 on 002. Shorten overly-long htrace span names for

[jira] [Commented] (HADOOP-11656) Classpath isolation for downstream clients

2015-03-04 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14347234#comment-14347234 ] stack commented on HADOOP-11656: bq. To add, I think we can and should strive for doing

[jira] [Commented] (HADOOP-11363) Hadoop maven surefire-plugin uses must set heap size

2014-12-08 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14238432#comment-14238432 ] stack commented on HADOOP-11363: lgtm Want to just go for 4G rather than 2G or you

[jira] [Commented] (HADOOP-11363) Hadoop maven surefire-plugin uses must set heap size

2014-12-08 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14238652#comment-14238652 ] stack commented on HADOOP-11363: +1 Hadoop maven surefire-plugin uses must set heap

[jira] [Commented] (HADOOP-11301) [optionally] update jmx cache to drop old metrics

2014-12-02 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14231887#comment-14231887 ] stack commented on HADOOP-11301: Just to say that this patch also fixes an issue in

[jira] [Updated] (HADOOP-11301) [optionally] update jmx cache to drop old metrics

2014-12-01 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-11301: --- Resolution: Fixed Fix Version/s: 2.7.0 Hadoop Flags: Reviewed Status: Resolved (was:

[jira] [Commented] (HADOOP-11301) [optionally] update jmx cache to drop old metrics

2014-12-01 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14231091#comment-14231091 ] stack commented on HADOOP-11301: Thanks [~ram_krish] Fixed. [optionally] update jmx

[jira] [Commented] (HADOOP-11301) [optionally] update jmx cache to drop old metrics

2014-11-26 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14226768#comment-14226768 ] stack commented on HADOOP-11301: We cache jmx values for 10ms only. Too short. The

[jira] [Commented] (HADOOP-11301) [optionally] update jmx cache to drop old metrics

2014-11-24 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14224164#comment-14224164 ] stack commented on HADOOP-11301: I tried the patch and it seems like it is doing as

[jira] [Commented] (HADOOP-11301) [optionally] update jmx cache to drop old metrics

2014-11-21 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14221485#comment-14221485 ] stack commented on HADOOP-11301: Looks much cleaner. Should these two statements be

[jira] [Commented] (HADOOP-11301) [optionally] update jmx cache to drop old metrics

2014-11-21 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14221610#comment-14221610 ] stack commented on HADOOP-11301: Lets go with your conservative suggestion. It will

[jira] [Commented] (HADOOP-11301) [optionally] update jmx cache to drop old metrics

2014-11-20 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14220356#comment-14220356 ] stack commented on HADOOP-11301: Agree with [~andrew.wang]. No need of a config. Can

[jira] [Commented] (HADOOP-10938) Remove thread-safe description in PositionedReadable javadoc

2014-11-03 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-10938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14195829#comment-14195829 ] stack commented on HADOOP-10938: I think this issue is going in the wrong direction.

[jira] [Commented] (HADOOP-11186) documentation should talk about hadoop.htrace.spanreceiver.classes, not hadoop.trace.spanreceiver.classes

2014-10-29 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-11186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188803#comment-14188803 ] stack commented on HADOOP-11186: +1 Small doc fix. Thanks [~cmccabe] documentation

[jira] [Commented] (HADOOP-10410) Support ioprio_set in NativeIO

2014-03-21 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-10410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13943307#comment-13943307 ] stack commented on HADOOP-10410: bq. I hope we can just do technical discussion in the

[jira] [Commented] (HADOOP-10410) Support ioprio_set in NativeIO

2014-03-21 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-10410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13943894#comment-13943894 ] stack commented on HADOOP-10410: bq. Why not get some experimental results, and then

[jira] [Commented] (HADOOP-10015) UserGroupInformation prints out excessive ERROR warnings

2014-03-20 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-10015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13942738#comment-13942738 ] stack commented on HADOOP-10015: I'd be +1 on DEBUG (Opening a new issue to discuss what

[jira] [Commented] (HADOOP-10410) Support ioprio_set in NativeIO

2014-03-18 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-10410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13939500#comment-13939500 ] stack commented on HADOOP-10410: Yeah [~xieliang007]... offline Todd suggested trying

[jira] [Commented] (HADOOP-10410) Support ioprio_set in NativeIO

2014-03-18 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-10410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13939640#comment-13939640 ] stack commented on HADOOP-10410: [~xieliang007] It'd be cool to try. One thought I had

[jira] [Updated] (HADOOP-10337) ConcurrentModificationException from MetricsDynamicMBeanBase.createMBeanInfo()

2014-03-10 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-10337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-10337: --- Resolution: Fixed Fix Version/s: 2.4.0 Hadoop Flags: Reviewed Status: Resolved

[jira] [Commented] (HADOOP-10313) Script and jenkins job to produce Hadoop release artifacts

2014-01-30 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13887263#comment-13887263 ] stack commented on HADOOP-10313: Alejandro, you want to add a bit of a comment on the

[jira] [Commented] (HADOOP-10313) Script and jenkins job to produce Hadoop release artifacts

2014-01-30 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13887474#comment-13887474 ] stack commented on HADOOP-10313: v2 lgtm Script and jenkins job to produce Hadoop

[jira] [Commented] (HADOOP-10255) Rename HttpServer to HttpServer2 to retain older HttpServer in branch-2 for compatibility

2014-01-28 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-10255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13884262#comment-13884262 ] stack commented on HADOOP-10255: [~sureshms] Thanks for committing. On 'We need to

  1   2   >