[jira] [Updated] (HADOOP-11891) OsSecureRandom should lazily fill its reservoir

[ https://issues.apache.org/jira/browse/HADOOP-11891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-11891: Fix Version/s: 2.8.0 > OsSecureRandom should lazily fill its reservoir >

[jira] [Updated] (HADOOP-8151) Error handling in snappy decompressor throws invalid exceptions

[ https://issues.apache.org/jira/browse/HADOOP-8151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-8151: --- Fix Version/s: 2.8.0 > Error handling in snappy decompressor throws invalid exceptions >

[jira] [Updated] (HADOOP-7139) Allow appending to existing SequenceFiles

[ https://issues.apache.org/jira/browse/HADOOP-7139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-7139: --- Fix Version/s: 2.8.0 > Allow appending to existing SequenceFiles >

[jira] [Updated] (HADOOP-13039) Add documentation for configuration property ipc.maximum.data.length for controlling maximum RPC message size.

[ https://issues.apache.org/jira/browse/HADOOP-13039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-13039: Fix Version/s: 2.8.0 > Add documentation for configuration property ipc.maximum.data.length for

[jira] [Updated] (HADOOP-12958) PhantomReference for filesystem statistics can trigger OOM

[ https://issues.apache.org/jira/browse/HADOOP-12958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-12958: Fix Version/s: 2.8.0 > PhantomReference for filesystem statistics can trigger OOM >

[jira] [Updated] (HADOOP-13052) ChecksumFileSystem mishandles crc file permissions

[ https://issues.apache.org/jira/browse/HADOOP-13052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-13052: Fix Version/s: 2.8.0 > ChecksumFileSystem mishandles crc file permissions >

[jira] [Updated] (HADOOP-12296) when setnetgrent returns 0 in linux, exception should be thrown

[ https://issues.apache.org/jira/browse/HADOOP-12296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-12296: Fix Version/s: 2.8.0 > when setnetgrent returns 0 in linux, exception should be thrown >

[jira] [Updated] (HADOOP-12078) The default retry policy does not handle RetriableException correctly

[ https://issues.apache.org/jira/browse/HADOOP-12078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-12078: Fix Version/s: 2.8.0 > The default retry policy does not handle RetriableException correctly >

[jira] [Updated] (HADOOP-11932) MetricsSinkAdapter hangs when being stopped

[ https://issues.apache.org/jira/browse/HADOOP-11932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-11932: Fix Version/s: 2.8.0 > MetricsSinkAdapter hangs when being stopped >

[jira] [Updated] (HADOOP-11966) Variable cygwin is undefined in hadoop-config.sh when executed through hadoop-daemon.sh.

[ https://issues.apache.org/jira/browse/HADOOP-11966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-11966: Fix Version/s: 2.8.0 > Variable cygwin is undefined in hadoop-config.sh when executed through >

[jira] [Updated] (HADOOP-13270) BZip2CompressionInputStream finds the same compression marker twice in corner case, causing duplicate data blocks

[ https://issues.apache.org/jira/browse/HADOOP-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-13270: Fix Version/s: 2.8.0 > BZip2CompressionInputStream finds the same compression marker twice in

[jira] [Updated] (HADOOP-13192) org.apache.hadoop.util.LineReader cannot handle multibyte delimiters correctly

[ https://issues.apache.org/jira/browse/HADOOP-13192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-13192: Fix Version/s: 2.8.0 > org.apache.hadoop.util.LineReader cannot handle multibyte delimiters

[jira] [Updated] (HADOOP-11491) HarFs incorrectly declared as requiring an authority

[ https://issues.apache.org/jira/browse/HADOOP-11491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-11491: Fix Version/s: 2.8.0 > HarFs incorrectly declared as requiring an authority >

[jira] [Updated] (HADOOP-13250) jdiff and dependency reports aren't linked in site web pages

[ https://issues.apache.org/jira/browse/HADOOP-13250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-13250: Target Version/s: 2.9.0, 3.0.0-alpha2 (was: 2.8.0, 3.0.0-alpha2) > jdiff and dependency reports

[jira] [Commented] (HADOOP-13250) jdiff and dependency reports aren't linked in site web pages

[ https://issues.apache.org/jira/browse/HADOOP-13250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15803012#comment-15803012 ] Junping Du commented on HADOOP-13250: - Sync with Vinod offline and push out from 2.8. > jdiff and

[jira] [Updated] (HADOOP-12577) Bump up commons-collections version to 3.2.2 to address a security flaw

[ https://issues.apache.org/jira/browse/HADOOP-12577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-12577: Fix Version/s: 2.8.0 > Bump up commons-collections version to 3.2.2 to address a security flaw >

[jira] [Updated] (HADOOP-11812) Implement listLocatedStatus for ViewFileSystem to speed up split calculation

[ https://issues.apache.org/jira/browse/HADOOP-11812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-11812: Fix Version/s: 2.8.0 > Implement listLocatedStatus for ViewFileSystem to speed up split

[jira] [Updated] (HADOOP-11934) Use of JavaKeyStoreProvider in LdapGroupsMapping causes infinite loop

[ https://issues.apache.org/jira/browse/HADOOP-11934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-11934: Fix Version/s: 2.8.0 > Use of JavaKeyStoreProvider in LdapGroupsMapping causes infinite loop >

[jira] [Updated] (HADOOP-12406) AbstractMapWritable.readFields throws ClassNotFoundException with custom writables

[ https://issues.apache.org/jira/browse/HADOOP-12406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-12406: Fix Version/s: 2.8.0 > AbstractMapWritable.readFields throws ClassNotFoundException with custom

[jira] [Commented] (HADOOP-12406) AbstractMapWritable.readFields throws ClassNotFoundException with custom writables

[ https://issues.apache.org/jira/browse/HADOOP-12406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802564#comment-15802564 ] Junping Du commented on HADOOP-12406: - Merge the fix to branch-2.8. >

[jira] [Commented] (HADOOP-13754) Hadoop-Azure Update WASB URI format to support SAS token in it.

[ https://issues.apache.org/jira/browse/HADOOP-13754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802532#comment-15802532 ] Junping Du commented on HADOOP-13754: - Hi, we should set fix version only until patch get committed.

[jira] [Updated] (HADOOP-13754) Hadoop-Azure Update WASB URI format to support SAS token in it.

[ https://issues.apache.org/jira/browse/HADOOP-13754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-13754: Fix Version/s: (was: 2.7.3) > Hadoop-Azure Update WASB URI format to support SAS token in it.

[jira] [Updated] (HADOOP-13754) Hadoop-Azure Update WASB URI format to support SAS token in it.

[ https://issues.apache.org/jira/browse/HADOOP-13754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-13754: Target Version/s: 2.9.0 (was: 2.7.3) > Hadoop-Azure Update WASB URI format to support SAS token

[jira] [Commented] (HADOOP-13774) Rest Loaded App fails

[ https://issues.apache.org/jira/browse/HADOOP-13774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802529#comment-15802529 ] Junping Du commented on HADOOP-13774: - Hi, we should set target version instead of fix version when

[jira] [Updated] (HADOOP-13774) Rest Loaded App fails

[ https://issues.apache.org/jira/browse/HADOOP-13774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-13774: Fix Version/s: (was: 2.7.3) > Rest Loaded App fails > - > >

[jira] [Commented] (HADOOP-13438) Optimize IPC server protobuf decoding

[ https://issues.apache.org/jira/browse/HADOOP-13438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802356#comment-15802356 ] Junping Du commented on HADOOP-13438: - If one JIRA is known to have typo commit messages (in your

[jira] [Updated] (HADOOP-9384) Update S3 native fs implementation to use AWS SDK to support authorization through roles

[ https://issues.apache.org/jira/browse/HADOOP-9384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-9384: --- Fix Version/s: (was: 2.7.1) > Update S3 native fs implementation to use AWS SDK to support

[jira] [Updated] (HADOOP-11851) s3n to swallow IOEs on inner stream close

[ https://issues.apache.org/jira/browse/HADOOP-11851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-11851: Fix Version/s: (was: 2.7.1) > s3n to swallow IOEs on inner stream close >

[jira] [Commented] (HADOOP-13438) Optimize IPC server protobuf decoding

[ https://issues.apache.org/jira/browse/HADOOP-13438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802314#comment-15802314 ] Junping Du commented on HADOOP-13438: - Thanks Andrew for share. My practice to make sure all JIRAs

[jira] [Commented] (HADOOP-13438) Optimize IPC server protobuf decoding

[ https://issues.apache.org/jira/browse/HADOOP-13438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15802215#comment-15802215 ] Junping Du commented on HADOOP-13438: - Got it. I also meet the same situation in other JIRAs later

[jira] [Updated] (HADOOP-12679) while performing the simple queries on s3 table through hive ,got exception:-Error: java.io.IOException: java.lang.reflect.InvocationTargetException

[ https://issues.apache.org/jira/browse/HADOOP-12679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-12679: Fix Version/s: (was: 2.7.1) > while performing the simple queries on s3 table through hive

[jira] [Updated] (HADOOP-9528) org.apache.hadoop.ha.TestZKFailoverController.testCedeActive is failing intermittently

[ https://issues.apache.org/jira/browse/HADOOP-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-9528: --- Target Version/s: (was: 2.9.0) > org.apache.hadoop.ha.TestZKFailoverController.testCedeActive is

[jira] [Updated] (HADOOP-9528) org.apache.hadoop.ha.TestZKFailoverController.testCedeActive is failing intermittently

[ https://issues.apache.org/jira/browse/HADOOP-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-9528: --- Target Version/s: 2.9.0 Fix Version/s: (was: 2.8.0) >

[jira] [Updated] (HADOOP-11573) verify that s3a handles / in secret key

[ https://issues.apache.org/jira/browse/HADOOP-11573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-11573: Fix Version/s: (was: 2.8.0) > verify that s3a handles / in secret key >

[jira] [Updated] (HADOOP-11942) Add links to SLGUserGuide to site index

[ https://issues.apache.org/jira/browse/HADOOP-11942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-11942: Fix Version/s: (was: 2.8.0) > Add links to SLGUserGuide to site index >

[jira] [Commented] (HADOOP-11942) Add links to SLGUserGuide to site index

[ https://issues.apache.org/jira/browse/HADOOP-11942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15799510#comment-15799510 ] Junping Du commented on HADOOP-11942: - This patch goes to trunk only. Remove 2.8 in fix version. >

[jira] [Commented] (HADOOP-12040) Adjust inputs order for the decode API in raw erasure coder

[ https://issues.apache.org/jira/browse/HADOOP-12040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15799507#comment-15799507 ] Junping Du commented on HADOOP-12040: - I believe this patch went only to trunk. Remove 2.8 from fix

[jira] [Updated] (HADOOP-12040) Adjust inputs order for the decode API in raw erasure coder

[ https://issues.apache.org/jira/browse/HADOOP-12040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-12040: Fix Version/s: (was: 2.8.0) > Adjust inputs order for the decode API in raw erasure coder >

[jira] [Commented] (HADOOP-12782) Faster LDAP group name resolution with ActiveDirectory

[ https://issues.apache.org/jira/browse/HADOOP-12782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15799470#comment-15799470 ] Junping Du commented on HADOOP-12782: - This patch is not landed in branch-2.8, mark fix version to

[jira] [Updated] (HADOOP-12782) Faster LDAP group name resolution with ActiveDirectory

[ https://issues.apache.org/jira/browse/HADOOP-12782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-12782: Fix Version/s: (was: 2.8.0) 2.9.0 > Faster LDAP group name resolution with

[jira] [Commented] (HADOOP-12787) KMS SPNEGO sequence does not work with WEBHDFS

[ https://issues.apache.org/jira/browse/HADOOP-12787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15799465#comment-15799465 ] Junping Du commented on HADOOP-12787: - Sounds like we are making a wrong JIRA number in commit. Make

[jira] [Commented] (HADOOP-12908) Make JvmPauseMonitor a singleton

[ https://issues.apache.org/jira/browse/HADOOP-12908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15799442#comment-15799442 ] Junping Du commented on HADOOP-12908: - Drop fix version as patch haven't be commit in. Adjust target

[jira] [Updated] (HADOOP-12908) Make JvmPauseMonitor a singleton

[ https://issues.apache.org/jira/browse/HADOOP-12908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-12908: Target Version/s: 2.9.0 (was: 2.8.0) > Make JvmPauseMonitor a singleton >

[jira] [Updated] (HADOOP-12908) Make JvmPauseMonitor a singleton

[ https://issues.apache.org/jira/browse/HADOOP-12908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-12908: Fix Version/s: (was: 2.8.0) > Make JvmPauseMonitor a singleton >

[jira] [Updated] (HADOOP-13102) Update GroupsMapping documentation to reflect the new changes

[ https://issues.apache.org/jira/browse/HADOOP-13102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-13102: Target Version/s: 2.9.0 (was: 2.8.0) Fix Version/s: (was: 2.8.0) The patch is not get

[jira] [Updated] (HADOOP-13009) add option for lazy open() on s3a

[ https://issues.apache.org/jira/browse/HADOOP-13009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-13009: Fix Version/s: (was: 2.8.0) > add option for lazy open() on s3a >

[jira] [Updated] (HADOOP-12978) move s3a to slf4j logging

[ https://issues.apache.org/jira/browse/HADOOP-12978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-12978: Fix Version/s: (was: 2.8.0) > move s3a to slf4j logging > - > >

[jira] [Updated] (HADOOP-13144) Enhancing IPC client throughput via multiple connections per user

[ https://issues.apache.org/jira/browse/HADOOP-13144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-13144: Target Version/s: 2.9.0 Fix Version/s: (was: 2.8.0) > Enhancing IPC client throughput

[jira] [Updated] (HADOOP-13367) Support more types of Store in S3Native File System

[ https://issues.apache.org/jira/browse/HADOOP-13367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-13367: Fix Version/s: (was: 2.8.0) > Support more types of Store in S3Native File System >

[jira] [Updated] (HADOOP-13438) Optimize IPC server protobuf decoding

[ https://issues.apache.org/jira/browse/HADOOP-13438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-13438: Fix Version/s: (was: 2.8.0) 2.9.0 > Optimize IPC server protobuf decoding

[jira] [Commented] (HADOOP-13438) Optimize IPC server protobuf decoding

[ https://issues.apache.org/jira/browse/HADOOP-13438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15799414#comment-15799414 ] Junping Du commented on HADOOP-13438: - This patch goes to branch-2 only instead of 2.8, set 2.9 as

[jira] [Commented] (HADOOP-13556) Change Configuration.getPropsWithPrefix to use getProps instead of iterator

[ https://issues.apache.org/jira/browse/HADOOP-13556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15799406#comment-15799406 ] Junping Du commented on HADOOP-13556: - The patch is not get in, so we should set target version

[jira] [Updated] (HADOOP-13556) Change Configuration.getPropsWithPrefix to use getProps instead of iterator

[ https://issues.apache.org/jira/browse/HADOOP-13556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-13556: Target Version/s: 2.9.0, 3.0.0-alpha2 Fix Version/s: (was: 3.0.0-alpha2)

[jira] [Commented] (HADOOP-13569) S3AFastOutputStream to take ProgressListener in file create()

[ https://issues.apache.org/jira/browse/HADOOP-13569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15799399#comment-15799399 ] Junping Du commented on HADOOP-13569: - Drop fix version for duplicated JIRAs. > S3AFastOutputStream

[jira] [Updated] (HADOOP-13569) S3AFastOutputStream to take ProgressListener in file create()

[ https://issues.apache.org/jira/browse/HADOOP-13569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-13569: Fix Version/s: (was: 2.8.0) > S3AFastOutputStream to take ProgressListener in file create() >

[jira] [Commented] (HADOOP-13703) S3ABlockOutputStream to pass Yetus & Jenkins

[ https://issues.apache.org/jira/browse/HADOOP-13703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15799396#comment-15799396 ] Junping Du commented on HADOOP-13703: - Drop 2.8 in fix version. > S3ABlockOutputStream to pass

[jira] [Updated] (HADOOP-13703) S3ABlockOutputStream to pass Yetus & Jenkins

[ https://issues.apache.org/jira/browse/HADOOP-13703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-13703: Fix Version/s: (was: 2.8.0) > S3ABlockOutputStream to pass Yetus & Jenkins >

[jira] [Updated] (HADOOP-13729) switch to Configuration.getLongBytes for byte options

[ https://issues.apache.org/jira/browse/HADOOP-13729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-13729: Fix Version/s: (was: 2.8.0) > switch to Configuration.getLongBytes for byte options >

[jira] [Commented] (HADOOP-13729) switch to Configuration.getLongBytes for byte options

[ https://issues.apache.org/jira/browse/HADOOP-13729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15799390#comment-15799390 ] Junping Du commented on HADOOP-13729: - Drop the version number given no commit from this jira get

[jira] [Commented] (HADOOP-13730) After 5 connection failures, yarn stops sending metrics graphite until restarted

[ https://issues.apache.org/jira/browse/HADOOP-13730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15799361#comment-15799361 ] Junping Du commented on HADOOP-13730: - Drop 2.8 in fix version. We should only set this value when

[jira] [Updated] (HADOOP-13730) After 5 connection failures, yarn stops sending metrics graphite until restarted

[ https://issues.apache.org/jira/browse/HADOOP-13730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-13730: Target Version/s: 2.9.0 Fix Version/s: (was: 2.8.0) > After 5 connection failures,

[jira] [Commented] (HADOOP-13755) Purge superfluous/obsolete S3A Tests

[ https://issues.apache.org/jira/browse/HADOOP-13755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15799357#comment-15799357 ] Junping Du commented on HADOOP-13755: - drop the fix version for duplicated ticket. > Purge

[jira] [Updated] (HADOOP-13755) Purge superfluous/obsolete S3A Tests

[ https://issues.apache.org/jira/browse/HADOOP-13755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-13755: Fix Version/s: (was: 2.8.0) > Purge superfluous/obsolete S3A Tests >

[jira] [Commented] (HADOOP-13848) Missing auth-keys.xml prevents detecting test code build problem

[ https://issues.apache.org/jira/browse/HADOOP-13848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15799291#comment-15799291 ] Junping Du commented on HADOOP-13848: - Drop fix version here as no commits going to branch-2.8. >

[jira] [Updated] (HADOOP-13848) Missing auth-keys.xml prevents detecting test code build problem

[ https://issues.apache.org/jira/browse/HADOOP-13848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-13848: Fix Version/s: (was: 2.8.0) > Missing auth-keys.xml prevents detecting test code build

[jira] [Commented] (HADOOP-13826) S3A Deadlock in multipart copy due to thread pool limits.

[ https://issues.apache.org/jira/browse/HADOOP-13826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15786517#comment-15786517 ] Junping Du commented on HADOOP-13826: - Hi [~ste...@apache.org] and [~mackrorysd], how close are we

[jira] [Updated] (HADOOP-13826) S3A Deadlock in multipart copy due to thread pool limits.

[ https://issues.apache.org/jira/browse/HADOOP-13826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-13826: Status: Patch Available (was: Open) > S3A Deadlock in multipart copy due to thread pool limits.

[jira] [Updated] (HADOOP-11626) Comment ReadStatistics to indicate that it tracks the actual read occurred

[ https://issues.apache.org/jira/browse/HADOOP-11626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-11626: Target Version/s: 2.9.0 (was: 2.8.0) > Comment ReadStatistics to indicate that it tracks the

[jira] [Commented] (HADOOP-11626) Comment ReadStatistics to indicate that it tracks the actual read occurred

[ https://issues.apache.org/jira/browse/HADOOP-11626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15717058#comment-15717058 ] Junping Du commented on HADOOP-11626: - Move this out of 2.8 given this jira don't make any progress

[jira] [Updated] (HADOOP-11626) Comment ReadStatistics to indicate that it tracks the actual read occurred

[ https://issues.apache.org/jira/browse/HADOOP-11626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-11626: Labels: (was: BB2015-05-TBR) > Comment ReadStatistics to indicate that it tracks the actual

[jira] [Updated] (HADOOP-12304) Applications using FileContext fail with the default file system configured to be wasb/s3/etc.

[ https://issues.apache.org/jira/browse/HADOOP-12304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-12304: Fix Version/s: 2.8.0 > Applications using FileContext fail with the default file system

[jira] [Updated] (HADOOP-5323) Trash documentation should describe its directory structure and configurations

[ https://issues.apache.org/jira/browse/HADOOP-5323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-5323: --- Fix Version/s: 2.8.0 > Trash documentation should describe its directory structure and

[jira] [Updated] (HADOOP-9242) Duplicate surefire plugin config in hadoop-common

[ https://issues.apache.org/jira/browse/HADOOP-9242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-9242: --- Fix Version/s: 2.8.0 > Duplicate surefire plugin config in hadoop-common >

[jira] [Commented] (HADOOP-12954) Add a way to change hadoop.security.token.service.use_ip

[ https://issues.apache.org/jira/browse/HADOOP-12954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15709522#comment-15709522 ] Junping Du commented on HADOOP-12954: - Hi Robert and Steve, do we want to backport this issue to 2.8

[jira] [Commented] (HADOOP-13826) S3A Deadlock in multipart copy due to thread pool limits.

[ https://issues.apache.org/jira/browse/HADOOP-13826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15709465#comment-15709465 ] Junping Du commented on HADOOP-13826: - Thanks Steve for nominating this into 2.8. I put this issue

[jira] [Updated] (HADOOP-13826) S3A Deadlock in multipart copy due to thread pool limits.

[ https://issues.apache.org/jira/browse/HADOOP-13826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-13826: Assignee: Sean Mackrory > S3A Deadlock in multipart copy due to thread pool limits. >

[jira] [Commented] (HADOOP-13362) DefaultMetricsSystem leaks the source name when a source unregisters

[ https://issues.apache.org/jira/browse/HADOOP-13362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15403140#comment-15403140 ] Junping Du commented on HADOOP-13362: - bq. 2.7.3 was in lockdown for only critical blockers that

[jira] [Commented] (HADOOP-13362) DefaultMetricsSystem leaks the source name when a source unregisters

[ https://issues.apache.org/jira/browse/HADOOP-13362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15402805#comment-15402805 ] Junping Du commented on HADOOP-13362: - Hi [~jlowe], forget to ask, any reason to not putting this

[jira] [Commented] (HADOOP-13362) DefaultMetricsSystem leaks the source name when a source unregisters

[ https://issues.apache.org/jira/browse/HADOOP-13362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15371645#comment-15371645 ] Junping Du commented on HADOOP-13362: - Thanks [~jlowe] for review and commit! >

[jira] [Updated] (HADOOP-13362) DefaultMetricsSystem leaks the source name when a source unregisters

[ https://issues.apache.org/jira/browse/HADOOP-13362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-13362: Status: Patch Available (was: Reopened) > DefaultMetricsSystem leaks the source name when a

[jira] [Updated] (HADOOP-13362) DefaultMetricsSystem leaks the source name when a source unregisters

[ https://issues.apache.org/jira/browse/HADOOP-13362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-13362: Attachment: HADOOP-13362-branch-2.7.patch > DefaultMetricsSystem leaks the source name when a

[jira] [Commented] (HADOOP-13362) DefaultMetricsSystem leaks the source name when a source unregisters

[ https://issues.apache.org/jira/browse/HADOOP-13362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15370943#comment-15370943 ] Junping Du commented on HADOOP-13362: - bq. The metrics are getting cleaned up in the monitoring

[jira] [Commented] (HADOOP-13362) DefaultMetricsSystem leaks the source name when a source unregisters

[ https://issues.apache.org/jira/browse/HADOOP-13362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15370908#comment-15370908 ] Junping Du commented on HADOOP-13362: - Ah. I think it is get called in ContainerDoneTransition.

[jira] [Commented] (HADOOP-13362) DefaultMetricsSystem leaks the source name when a source unregisters

[ https://issues.apache.org/jira/browse/HADOOP-13362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15370899#comment-15370899 ] Junping Du commented on HADOOP-13362: - bq. Note that we've not seen the uncaught exception issue

[jira] [Commented] (HADOOP-13362) DefaultMetricsSystem leaks the source name when a source unregisters

[ https://issues.apache.org/jira/browse/HADOOP-13362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15370785#comment-15370785 ] Junping Du commented on HADOOP-13362: - Hi [~jlowe], as I mentioned in YARN-5296, I think the work

[jira] [Updated] (HADOOP-11134) Change the default log level of interactive commands from INFO to WARN

[ https://issues.apache.org/jira/browse/HADOOP-11134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-11134: Target Version/s: (was: ) Hadoop Flags: Incompatible change > Change the default log

[jira] [Commented] (HADOOP-10048) LocalDirAllocator should avoid holding locks while accessing the filesystem

[ https://issues.apache.org/jira/browse/HADOOP-10048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15342775#comment-15342775 ] Junping Du commented on HADOOP-10048: - I would prefer not to backport to 2.6 and 2.7 for the same

[jira] [Updated] (HADOOP-10048) LocalDirAllocator should avoid holding locks while accessing the filesystem

[ https://issues.apache.org/jira/browse/HADOOP-10048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-10048: Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: 2.8.0 Status:

[jira] [Commented] (HADOOP-13184) Add "Apache" to Hadoop project logo

[ https://issues.apache.org/jira/browse/HADOOP-13184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15318485#comment-15318485 ] Junping Du commented on HADOOP-13184: - +1 on option 4 too. > Add "Apache" to Hadoop project logo >

[jira] [Commented] (HADOOP-10048) LocalDirAllocator should avoid holding locks while accessing the filesystem

[ https://issues.apache.org/jira/browse/HADOOP-10048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15316672#comment-15316672 ] Junping Du commented on HADOOP-10048: - Thanks [~jlowe] for updating the patch. bq. All or most of

[jira] [Commented] (HADOOP-10048) LocalDirAllocator should avoid holding locks while accessing the filesystem

[ https://issues.apache.org/jira/browse/HADOOP-10048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15301081#comment-15301081 ] Junping Du commented on HADOOP-10048: - bq. No, that could trigger an array bounds exception if we

[jira] [Commented] (HADOOP-10048) LocalDirAllocator should avoid holding locks while accessing the filesystem

[ https://issues.apache.org/jira/browse/HADOOP-10048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15300600#comment-15300600 ] Junping Du commented on HADOOP-10048: - Thanks [~jlowe] for updating the patch! 005 patch looks good

[jira] [Commented] (HADOOP-10048) LocalDirAllocator should avoid holding locks while accessing the filesystem

[ https://issues.apache.org/jira/browse/HADOOP-10048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15299261#comment-15299261 ] Junping Du commented on HADOOP-10048: - Thanks [~jlowe] for updating the patch. I am OK with lockless

[jira] [Updated] (HADOOP-12074) in Shell.java#runCommand() rethrow InterruptedException as InterruptedIOException

[ https://issues.apache.org/jira/browse/HADOOP-12074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-12074: Priority: Minor (was: Trivial) > in Shell.java#runCommand() rethrow InterruptedException as >

[jira] [Commented] (HADOOP-10048) LocalDirAllocator should avoid holding locks while accessing the filesystem

[ https://issues.apache.org/jira/browse/HADOOP-10048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15292506#comment-15292506 ] Junping Du commented on HADOOP-10048: - The patch is a bit old. Kick off Jenkins test manually again.

[jira] [Updated] (HADOOP-10048) LocalDirAllocator should avoid holding locks while accessing the filesystem

[ https://issues.apache.org/jira/browse/HADOOP-10048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-10048: Labels: (was: BB2015-05-TBR) > LocalDirAllocator should avoid holding locks while accessing the

[jira] [Updated] (HADOOP-13098) Dynamic LogLevel setting page should accept log level string with mixing upper case and lower case

[ https://issues.apache.org/jira/browse/HADOOP-13098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-13098: Attachment: HADOOP-13098-v3.patch Thanks for reviewing this, [~xyao]! Fix this silly issue in v3

[jira] [Updated] (HADOOP-13098) Dynamic LogLevel setting page should accept log level string with mixing upper case and lower case

[ https://issues.apache.org/jira/browse/HADOOP-13098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-13098: Attachment: HADOOP-13098-v2.patch Thanks [~liuml07] for review! v2 patch incorporate your

[jira] [Updated] (HADOOP-13098) Dynamic LogLevel setting page should accept log level string with mixing upper case and lower case

[ https://issues.apache.org/jira/browse/HADOOP-13098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-13098: Target Version/s: 2.8.0 Status: Patch Available (was: Open) > Dynamic LogLevel

[jira] [Updated] (HADOOP-13098) Dynamic LogLevel setting page should accept log level string with mixing upper case and lower case

[ https://issues.apache.org/jira/browse/HADOOP-13098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated HADOOP-13098: Attachment: HADOOP-13098.patch Put a patch to fix this issue. > Dynamic LogLevel setting page

<    1   2   3   4   5   6   7   8   9   >