[jira] [Commented] (HBASE-15080) Remove synchronized block from MasterServiceStubMaker#releaseZooKeeperWatcher()

2016-01-09 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-15080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15090580#comment-15090580
 ] 

Hudson commented on HBASE-15080:


FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #1158 (See 
[https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/1158/])
HBASE-15080 Remove synchronized block from (tedyu: rev 
1f23667a827faf2bc2cc6c2ff6b14d29b733d046)
* 
hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java


> Remove synchronized block from 
> MasterServiceStubMaker#releaseZooKeeperWatcher()
> ---
>
> Key: HBASE-15080
> URL: https://issues.apache.org/jira/browse/HBASE-15080
> Project: HBase
>  Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
> Fix For: 0.98.17
>
> Attachments: 15080-0.98.txt
>
>
> This is a follow up to HBASE-11460
> [~elserj] found that in 0.98, the synchronized block below should have been 
> taken out (as was done for branch-1 +):
> {code}
>   synchronized (masterAndZKLock) {
> if (keepAliveZookeeperUserCount.decrementAndGet() <= 0 ){
> {code}
> keepAliveZookeeperUserCount is an AtomicInteger. There is no need for the 
> synchronized block.
> This issue is to remove the synchronized block.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-15085) IllegalStateException was thrown when scanning on bulkloaded HFiles

2016-01-09 Thread Victor Xu (JIRA)

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

Victor Xu updated HBASE-15085:
--
Attachment: HBASE-15085-v1.patch

Submit patch for both master and  branch-1.

> IllegalStateException was thrown when scanning on bulkloaded HFiles
> ---
>
> Key: HBASE-15085
> URL: https://issues.apache.org/jira/browse/HBASE-15085
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 0.98.12, 1.1.2
> Environment: HBase-0.98.12 & Hadoop-2.6.0 & JDK1.7
> HBase-1.1.2 & Hadoop-2.6.0 & JDK1.7
>Reporter: Victor Xu
>Assignee: Victor Xu
>  Labels: hfile
> Attachments: HBASE-15085-0.98-v1.patch, HBASE-15085-v1.patch
>
>
> IllegalStateException was thrown when we scanned from an HFile which was bulk 
> loaded several minutes ago, as shown below:
> {code}
> 2015-12-16 22:20:54,456 ERROR 
> com.taobao.kart.coprocessor.server.KartCoprocessor: 
> icbu_ae_ws_product,/0055,1450275490479.6a6a700f465ad074287fed720c950f7c. 
> batchNotify exception
> java.lang.IllegalStateException: EncodedScanner works only on encoded data 
> blocks
> at 
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$EncodedScannerV2.updateCurrentBlock(HFileReaderV2.java:1042)
> at 
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$EncodedScannerV2.seekTo(HFileReaderV2.java:1093)
> at 
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.seekAtOrAfter(StoreFileScanner.java:244)
> at 
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.seek(StoreFileScanner.java:152)
> at 
> org.apache.hadoop.hbase.regionserver.StoreScanner.seekScanners(StoreScanner.java:329)
> at 
> org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:188)
> at 
> org.apache.hadoop.hbase.regionserver.HStore.getScanner(HStore.java:1879)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.(HRegion.java:4068)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.instantiateRegionScanner(HRegion.java:2029)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2015)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:1992)
> {code}
> I used 'hbase hfile' command to analyse the meta and block info of the hfile, 
> finding that even through the DATA_BLOCK_ENCODING was 'DIFF' in FileInfo, the 
> actual data blocks was written without any encoding algorithms(BlockType was 
> 'DATA', not 'ENCODED_DATA'):
> {code}
> Fileinfo:
> BLOOM_FILTER_TYPE = ROW
> BULKLOAD_SOURCE_TASK = attempt_1442077249005_606706_r_12_0
> BULKLOAD_TIMESTAMP = \x00\x00\x01R\x12$\x13\x12
> DATA_BLOCK_ENCODING = DIFF
> ...
> DataBlock Header:
> HFileBlock [ fileOffset=0 headerSize()=33 blockType=DATA 
> onDiskSizeWithoutHeader=65591 uncompressedSizeWithoutHeader=65571 
> prevBlockOffset=-1 isUseHBaseChecksum()=true checksumType=CRC32 
> bytesPerChecksum=16384 onDiskDataSizeWithHeader=65604 
> getOnDiskSizeWithHeader()=65624 totalChecksumBytes()=20 isUnpacked()=true 
> buf=[ java.nio.HeapByteBuffer[pos=0 lim=65624 cap=65657], 
> array().length=65657, arrayOffset()=0 ] 
> dataBeginsWith=\x00\x00\x003\x00\x00\x00\x0A\x00\x10/0008:18\x01dprod 
> fileContext=HFileContext [ usesHBaseChecksum=true checksumType=CRC32 
> bytesPerChecksum=16384 blocksize=65536 encoding=NONE includesMvcc=true 
> includesTags=false compressAlgo=NONE compressTags=false cryptoContext=[ 
> cipher=NONE keyHash=NONE ] ] ]
> {code}
> The data block encoding in file info was not consistent with the one in data 
> block, which means there must be something wrong with the bulkload process.
> After debugging on each step of bulkload, I found that LoadIncrementalHFiles 
> had a bug when loading hfile into a splitted region. 
> {code}
> /**
>* Copy half of an HFile into a new HFile.
>*/
>   private static void copyHFileHalf(
>   Configuration conf, Path inFile, Path outFile, Reference reference,
>   HColumnDescriptor familyDescriptor)
>   throws IOException {
> FileSystem fs = inFile.getFileSystem(conf);
> CacheConfig cacheConf = new CacheConfig(conf);
> HalfStoreFileReader halfReader = null;
> StoreFile.Writer halfWriter = null;
> try {
>   halfReader = new HalfStoreFileReader(fs, inFile, cacheConf, reference, 
> conf);
>   Map fileInfo = halfReader.loadFileInfo();
>   int blocksize = familyDescriptor.getBlocksize();
>   Algorithm compression = familyDescriptor.getCompression();
>   BloomType bloomFilterType = familyDescriptor.getBloomFilterType();
> // use CF's DATA_BLOCK_ENCODING to initialize HFile writer
>   HFileContext hFileContext = new HFileContextBuilder()
>   

[jira] [Updated] (HBASE-15085) IllegalStateException was thrown when scanning on bulkloaded HFiles

2016-01-09 Thread Victor Xu (JIRA)

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

Victor Xu updated HBASE-15085:
--
Attachment: HBASE-15085-0.98-v1.patch

Attach patch for 0.98 branch.

> IllegalStateException was thrown when scanning on bulkloaded HFiles
> ---
>
> Key: HBASE-15085
> URL: https://issues.apache.org/jira/browse/HBASE-15085
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 0.98.12, 1.1.2
> Environment: HBase-0.98.12 & Hadoop-2.6.0 & JDK1.7
> HBase-1.1.2 & Hadoop-2.6.0 & JDK1.7
>Reporter: Victor Xu
>Assignee: Victor Xu
>  Labels: hfile
> Attachments: HBASE-15085-0.98-v1.patch, HBASE-15085-v1.patch
>
>
> IllegalStateException was thrown when we scanned from an HFile which was bulk 
> loaded several minutes ago, as shown below:
> {code}
> 2015-12-16 22:20:54,456 ERROR 
> com.taobao.kart.coprocessor.server.KartCoprocessor: 
> icbu_ae_ws_product,/0055,1450275490479.6a6a700f465ad074287fed720c950f7c. 
> batchNotify exception
> java.lang.IllegalStateException: EncodedScanner works only on encoded data 
> blocks
> at 
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$EncodedScannerV2.updateCurrentBlock(HFileReaderV2.java:1042)
> at 
> org.apache.hadoop.hbase.io.hfile.HFileReaderV2$EncodedScannerV2.seekTo(HFileReaderV2.java:1093)
> at 
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.seekAtOrAfter(StoreFileScanner.java:244)
> at 
> org.apache.hadoop.hbase.regionserver.StoreFileScanner.seek(StoreFileScanner.java:152)
> at 
> org.apache.hadoop.hbase.regionserver.StoreScanner.seekScanners(StoreScanner.java:329)
> at 
> org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:188)
> at 
> org.apache.hadoop.hbase.regionserver.HStore.getScanner(HStore.java:1879)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.(HRegion.java:4068)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.instantiateRegionScanner(HRegion.java:2029)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2015)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:1992)
> {code}
> I used 'hbase hfile' command to analyse the meta and block info of the hfile, 
> finding that even through the DATA_BLOCK_ENCODING was 'DIFF' in FileInfo, the 
> actual data blocks was written without any encoding algorithms(BlockType was 
> 'DATA', not 'ENCODED_DATA'):
> {code}
> Fileinfo:
> BLOOM_FILTER_TYPE = ROW
> BULKLOAD_SOURCE_TASK = attempt_1442077249005_606706_r_12_0
> BULKLOAD_TIMESTAMP = \x00\x00\x01R\x12$\x13\x12
> DATA_BLOCK_ENCODING = DIFF
> ...
> DataBlock Header:
> HFileBlock [ fileOffset=0 headerSize()=33 blockType=DATA 
> onDiskSizeWithoutHeader=65591 uncompressedSizeWithoutHeader=65571 
> prevBlockOffset=-1 isUseHBaseChecksum()=true checksumType=CRC32 
> bytesPerChecksum=16384 onDiskDataSizeWithHeader=65604 
> getOnDiskSizeWithHeader()=65624 totalChecksumBytes()=20 isUnpacked()=true 
> buf=[ java.nio.HeapByteBuffer[pos=0 lim=65624 cap=65657], 
> array().length=65657, arrayOffset()=0 ] 
> dataBeginsWith=\x00\x00\x003\x00\x00\x00\x0A\x00\x10/0008:18\x01dprod 
> fileContext=HFileContext [ usesHBaseChecksum=true checksumType=CRC32 
> bytesPerChecksum=16384 blocksize=65536 encoding=NONE includesMvcc=true 
> includesTags=false compressAlgo=NONE compressTags=false cryptoContext=[ 
> cipher=NONE keyHash=NONE ] ] ]
> {code}
> The data block encoding in file info was not consistent with the one in data 
> block, which means there must be something wrong with the bulkload process.
> After debugging on each step of bulkload, I found that LoadIncrementalHFiles 
> had a bug when loading hfile into a splitted region. 
> {code}
> /**
>* Copy half of an HFile into a new HFile.
>*/
>   private static void copyHFileHalf(
>   Configuration conf, Path inFile, Path outFile, Reference reference,
>   HColumnDescriptor familyDescriptor)
>   throws IOException {
> FileSystem fs = inFile.getFileSystem(conf);
> CacheConfig cacheConf = new CacheConfig(conf);
> HalfStoreFileReader halfReader = null;
> StoreFile.Writer halfWriter = null;
> try {
>   halfReader = new HalfStoreFileReader(fs, inFile, cacheConf, reference, 
> conf);
>   Map fileInfo = halfReader.loadFileInfo();
>   int blocksize = familyDescriptor.getBlocksize();
>   Algorithm compression = familyDescriptor.getCompression();
>   BloomType bloomFilterType = familyDescriptor.getBloomFilterType();
> // use CF's DATA_BLOCK_ENCODING to initialize HFile writer
>   HFileContext hFileContext = new HFileContextBuilder()
>   .withCompression(compression)
>   

[jira] [Created] (HBASE-15085) IllegalStateException was thrown when scanning on bulkloaded HFiles

2016-01-09 Thread Victor Xu (JIRA)
Victor Xu created HBASE-15085:
-

 Summary: IllegalStateException was thrown when scanning on 
bulkloaded HFiles
 Key: HBASE-15085
 URL: https://issues.apache.org/jira/browse/HBASE-15085
 Project: HBase
  Issue Type: Bug
Affects Versions: 1.1.2, 0.98.12
 Environment: HBase-0.98.12 & Hadoop-2.6.0 & JDK1.7
HBase-1.1.2 & Hadoop-2.6.0 & JDK1.7
Reporter: Victor Xu
Assignee: Victor Xu


IllegalStateException was thrown when we scanned from an HFile which was bulk 
loaded several minutes ago, as shown below:
{code}
2015-12-16 22:20:54,456 ERROR 
com.taobao.kart.coprocessor.server.KartCoprocessor: 
icbu_ae_ws_product,/0055,1450275490479.6a6a700f465ad074287fed720c950f7c. 
batchNotify exception
java.lang.IllegalStateException: EncodedScanner works only on encoded data 
blocks
at 
org.apache.hadoop.hbase.io.hfile.HFileReaderV2$EncodedScannerV2.updateCurrentBlock(HFileReaderV2.java:1042)
at 
org.apache.hadoop.hbase.io.hfile.HFileReaderV2$EncodedScannerV2.seekTo(HFileReaderV2.java:1093)
at 
org.apache.hadoop.hbase.regionserver.StoreFileScanner.seekAtOrAfter(StoreFileScanner.java:244)
at 
org.apache.hadoop.hbase.regionserver.StoreFileScanner.seek(StoreFileScanner.java:152)
at 
org.apache.hadoop.hbase.regionserver.StoreScanner.seekScanners(StoreScanner.java:329)
at 
org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:188)
at 
org.apache.hadoop.hbase.regionserver.HStore.getScanner(HStore.java:1879)
at 
org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.(HRegion.java:4068)
at 
org.apache.hadoop.hbase.regionserver.HRegion.instantiateRegionScanner(HRegion.java:2029)
at 
org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2015)
at 
org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:1992)
{code}
I used 'hbase hfile' command to analyse the meta and block info of the hfile, 
finding that even through the DATA_BLOCK_ENCODING was 'DIFF' in FileInfo, the 
actual data blocks was written without any encoding algorithms(BlockType was 
'DATA', not 'ENCODED_DATA'):
{code}
Fileinfo:
BLOOM_FILTER_TYPE = ROW
BULKLOAD_SOURCE_TASK = attempt_1442077249005_606706_r_12_0
BULKLOAD_TIMESTAMP = \x00\x00\x01R\x12$\x13\x12
DATA_BLOCK_ENCODING = DIFF
...
DataBlock Header:
HFileBlock [ fileOffset=0 headerSize()=33 blockType=DATA 
onDiskSizeWithoutHeader=65591 uncompressedSizeWithoutHeader=65571 
prevBlockOffset=-1 isUseHBaseChecksum()=true checksumType=CRC32 
bytesPerChecksum=16384 onDiskDataSizeWithHeader=65604 
getOnDiskSizeWithHeader()=65624 totalChecksumBytes()=20 isUnpacked()=true buf=[ 
java.nio.HeapByteBuffer[pos=0 lim=65624 cap=65657], array().length=65657, 
arrayOffset()=0 ] 
dataBeginsWith=\x00\x00\x003\x00\x00\x00\x0A\x00\x10/0008:18\x01dprod 
fileContext=HFileContext [ usesHBaseChecksum=true checksumType=CRC32 
bytesPerChecksum=16384 blocksize=65536 encoding=NONE includesMvcc=true 
includesTags=false compressAlgo=NONE compressTags=false cryptoContext=[ 
cipher=NONE keyHash=NONE ] ] ]
{code}
The data block encoding in file info was not consistent with the one in data 
block, which means there must be something wrong with the bulkload process.
After debugging on each step of bulkload, I found that LoadIncrementalHFiles 
had a bug when loading hfile into a splitted region. 
{code}
/**
   * Copy half of an HFile into a new HFile.
   */
  private static void copyHFileHalf(
  Configuration conf, Path inFile, Path outFile, Reference reference,
  HColumnDescriptor familyDescriptor)
  throws IOException {
FileSystem fs = inFile.getFileSystem(conf);
CacheConfig cacheConf = new CacheConfig(conf);
HalfStoreFileReader halfReader = null;
StoreFile.Writer halfWriter = null;
try {
  halfReader = new HalfStoreFileReader(fs, inFile, cacheConf, reference, 
conf);
  Map fileInfo = halfReader.loadFileInfo();

  int blocksize = familyDescriptor.getBlocksize();
  Algorithm compression = familyDescriptor.getCompression();
  BloomType bloomFilterType = familyDescriptor.getBloomFilterType();
// use CF's DATA_BLOCK_ENCODING to initialize HFile writer
  HFileContext hFileContext = new HFileContextBuilder()
  .withCompression(compression)
  
.withChecksumType(HStore.getChecksumType(conf))
  
.withBytesPerCheckSum(HStore.getBytesPerChecksum(conf))
  .withBlockSize(blocksize)
  
.withDataBlockEncoding(familyDescriptor.getDataBlockEncoding())
  .build();
  halfWriter = new StoreFile.WriterBuilder(conf, cacheConf,
  fs)
  .withFilePath(outFile)
  

[jira] [Commented] (HBASE-15084) Remove references to repository.codehaus.org

2016-01-09 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-15084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15090799#comment-15090799
 ] 

Hudson commented on HBASE-15084:


SUCCESS: Integrated in HBase-0.94-security #593 (See 
[https://builds.apache.org/job/HBase-0.94-security/593/])
HBASE-15084 Remove references to repository.codehaus.org. (larsh: rev 
a25e9bebfee584505e994f8ff5354336f2b46f24)
* pom.xml


> Remove references to repository.codehaus.org
> 
>
> Key: HBASE-15084
> URL: https://issues.apache.org/jira/browse/HBASE-15084
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 0.94.27
>Reporter: Lars Hofhansl
>Assignee: Lars Hofhansl
> Fix For: 0.94.28
>
>
> repository.codehause.org is not longer active.
> A dns-lookup reveals an alias to stop-looking-at.repository-codehaus-org :)
> All repositories have been moved to Maven central, so it can just removed 
> from the pom.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-15016) StoreServices facility in Region

2016-01-09 Thread stack (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-15016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15090805#comment-15090805
 ] 

stack commented on HBASE-15016:
---

Let me have a go at it... will be back.. [~eshcar]

> StoreServices facility in Region
> 
>
> Key: HBASE-15016
> URL: https://issues.apache.org/jira/browse/HBASE-15016
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Eshcar Hillel
>Assignee: Eshcar Hillel
> Attachments: HBASE-15016-V01.patch, HBASE-15016-V02.patch, 
> HBASE-15016-V03.patch, Regioncounters.pdf, suggestion.patch
>
>
> The default implementation of a memstore ensures that between two flushes the 
> memstore size increases monotonically. Supporting new memstores that store 
> data in different formats (specifically, compressed), or that allows to 
> eliminate data redundancies in memory (e.g., via compaction), means that the 
> size of the data stored in memory can decrease even between two flushes. This 
> requires memstores to have access to facilities that manipulate region 
> counters and synchronization.
> This subtasks introduces a new region interface -- StoreServices, through 
> which store components can access these facilities.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-15082) Fix merge of MVCC and SequenceID performance regression

2016-01-09 Thread stack (JIRA)

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

stack updated HBASE-15082:
--
Attachment: 15082v2.patch

Findbugs complaints are not from this patch. Trying to address in another 
issue. The rest is mine though. Here is another attempt.

{code}
if a thread A begins a transaction writing row A and then thread B beings a
transaction on row B, but then thread B completes and thread A does not...
A subsequent read of row B will not see the most recent write on this row
because the read point has not caught up because the outstanding mvcc write
from thread A will hold up the complete of the thread B mvcc complete; its
this latter that will catch up the mvcc read point. In branch-1, we did
a read uncommitted to get around this fact. TODO: Add test here.

This patch is a forward port of the branch-1 'fix'. Also does refactor
of a few methods that were copy/pastes of each other: increment and append
as well as checkAndMutate and checkAndRowMutation.

M b/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Scan.java
  Pass on any isolation level specified.

M b/hbase-client/src/test/java/org/apache/hadoop/hbase/client/TestIncrement.java
  Give test a proper name.

M  b/hbase-common/src/main/java/org/apache/hadoop/hbase/TagUtil.java
  Added utility methods carryForwardTags and carryForwardTTLTag.

M 
b/hbase-examples/src/main/java/org/apache/hadoop/hbase/coprocessor/example/ZooKeeperScanPolicyObserver.java
  Fix method capitalization

M b/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
  Move all mvcc completes and syncs under row lock. While I'm at it, since sync 
is
  now under row lock, move update of memstore AFTER sync-to-WAL. Allows for 
simplification
  Removed guts of a DLR method, setRecovering. Doesn't work and unsupported 
since 1.2.
  Fixed capitialization on getReadpoint.
  Tried to break up a few massive methods.

D 
b/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/wal/ReplayHLogKey.java
  Removed. From DLR.

M  b/hbase-server/src/main/java/org/apache/hadoop/hbase/wal/WALKey.java
  Add utility completeMvcc

A  
b/hbase-server/src/test/java/org/apache/hadoop/hbase/IncrementPerformanceTest.java
  Added simple increment test.
{code}

> Fix merge of MVCC and SequenceID performance regression
> ---
>
> Key: HBASE-15082
> URL: https://issues.apache.org/jira/browse/HBASE-15082
> Project: HBase
>  Issue Type: Sub-task
>  Components: Performance
>Reporter: stack
>Assignee: stack
>Priority: Critical
> Fix For: 2.0.0, 1.2.0, 1.3.0
>
> Attachments: 15082.patch, 15082v2.patch, 15082v2.txt, 15082v3.txt, 
> 15082v4.patch, 15082v5.patch
>
>
> This is general fix for increments (appends, checkAnd*) perf-regression 
> identified in the parent issue. HBASE-15031 has a narrow fix for branch-1.1 
> and branch-1.0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-15016) StoreServices facility in Region

2016-01-09 Thread Eshcar Hillel (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-15016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15090776#comment-15090776
 ] 

Eshcar Hillel commented on HBASE-15016:
---

Sure it would help if you have a clean version.
As a matter of fact perhaps a clean version of your patch is all that is needed 
for this sub-task, while the flush policy which is tightly coupled with 
compacting memstores and additional changes to column descriptor like adding 
isCompacting() method should be part of sub-task #3 where we actually declare 
the new class.
What do you say?

> StoreServices facility in Region
> 
>
> Key: HBASE-15016
> URL: https://issues.apache.org/jira/browse/HBASE-15016
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Eshcar Hillel
>Assignee: Eshcar Hillel
> Attachments: HBASE-15016-V01.patch, HBASE-15016-V02.patch, 
> HBASE-15016-V03.patch, Regioncounters.pdf, suggestion.patch
>
>
> The default implementation of a memstore ensures that between two flushes the 
> memstore size increases monotonically. Supporting new memstores that store 
> data in different formats (specifically, compressed), or that allows to 
> eliminate data redundancies in memory (e.g., via compaction), means that the 
> size of the data stored in memory can decrease even between two flushes. This 
> requires memstores to have access to facilities that manipulate region 
> counters and synchronization.
> This subtasks introduces a new region interface -- StoreServices, through 
> which store components can access these facilities.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-15087) Fix hbase-common findbugs complaints

2016-01-09 Thread stack (JIRA)

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

stack updated HBASE-15087:
--
Attachment: 15087.patch

For hase-common findbugs complaints

> Fix hbase-common findbugs complaints
> 
>
> Key: HBASE-15087
> URL: https://issues.apache.org/jira/browse/HBASE-15087
> Project: HBase
>  Issue Type: Sub-task
>  Components: build
>Reporter: stack
> Attachments: 15087.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-15084) Remove references to repository.codehaus.org

2016-01-09 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-15084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15090803#comment-15090803
 ] 

Hudson commented on HBASE-15084:


FAILURE: Integrated in HBase-0.94-JDK7 #252 (See 
[https://builds.apache.org/job/HBase-0.94-JDK7/252/])
HBASE-15084 Remove references to repository.codehaus.org. (larsh: rev 
a25e9bebfee584505e994f8ff5354336f2b46f24)
* pom.xml


> Remove references to repository.codehaus.org
> 
>
> Key: HBASE-15084
> URL: https://issues.apache.org/jira/browse/HBASE-15084
> Project: HBase
>  Issue Type: Bug
>Affects Versions: 0.94.27
>Reporter: Lars Hofhansl
>Assignee: Lars Hofhansl
> Fix For: 0.94.28
>
>
> repository.codehause.org is not longer active.
> A dns-lookup reveals an alias to stop-looking-at.repository-codehaus-org :)
> All repositories have been moved to Maven central, so it can just removed 
> from the pom.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-15080) Remove synchronized block from MasterServiceStubMaker#releaseZooKeeperWatcher()

2016-01-09 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-15080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15090695#comment-15090695
 ] 

Hudson commented on HBASE-15080:


SUCCESS: Integrated in HBase-0.98-matrix #284 (See 
[https://builds.apache.org/job/HBase-0.98-matrix/284/])
HBASE-15080 Remove synchronized block from (tedyu: rev 
1f23667a827faf2bc2cc6c2ff6b14d29b733d046)
* 
hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java


> Remove synchronized block from 
> MasterServiceStubMaker#releaseZooKeeperWatcher()
> ---
>
> Key: HBASE-15080
> URL: https://issues.apache.org/jira/browse/HBASE-15080
> Project: HBase
>  Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Ted Yu
> Fix For: 0.98.17
>
> Attachments: 15080-0.98.txt
>
>
> This is a follow up to HBASE-11460
> [~elserj] found that in 0.98, the synchronized block below should have been 
> taken out (as was done for branch-1 +):
> {code}
>   synchronized (masterAndZKLock) {
> if (keepAliveZookeeperUserCount.decrementAndGet() <= 0 ){
> {code}
> keepAliveZookeeperUserCount is an AtomicInteger. There is no need for the 
> synchronized block.
> This issue is to remove the synchronized block.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (HBASE-15087) Fix hbase-common findbugs complaints

2016-01-09 Thread stack (JIRA)
stack created HBASE-15087:
-

 Summary: Fix hbase-common findbugs complaints
 Key: HBASE-15087
 URL: https://issues.apache.org/jira/browse/HBASE-15087
 Project: HBase
  Issue Type: Sub-task
Reporter: stack






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (HBASE-15086) Fix findbugs complaint so yetus reports more green

2016-01-09 Thread stack (JIRA)
stack created HBASE-15086:
-

 Summary: Fix findbugs complaint so yetus reports more green
 Key: HBASE-15086
 URL: https://issues.apache.org/jira/browse/HBASE-15086
 Project: HBase
  Issue Type: Umbrella
  Components: build
Reporter: stack


Umbrella issue for findbugs fixings. The red complaints in yetus report look 
ugly. Lets fix. There ain't too many. This is umbrella issue. Can do a 
component at a time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-14763) Remove usages of deprecated HConnection

2016-01-09 Thread Jonathan Hsieh (JIRA)

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

Jonathan Hsieh updated HBASE-14763:
---
Attachment: hbase-14763.v6.patch

This went stale.  v6 gets it up to date with current trunk.

> Remove usages of deprecated HConnection 
> 
>
> Key: HBASE-14763
> URL: https://issues.apache.org/jira/browse/HBASE-14763
> Project: HBase
>  Issue Type: Bug
>  Components: hbase
>Affects Versions: 2.0.0
>Reporter: Jonathan Hsieh
>Assignee: Jonathan Hsieh
> Fix For: 2.0.0
>
> Attachments: hbase-14763.patch, hbase-14763.v2.patch, 
> hbase-14763.v3.patch, hbase-14763.v3.patch, hbase-14763.v4.patch, 
> hbase-14763.v5.patch, hbase-14763.v6.patch
>
>
> HConnection was deprecated in 1.0.0.  There are two interfaces that are 
> supposed to be used instead -- Connection for client programs and 
> ClusterConnection for internal hbaes and special tools (LoadIncremental, 
> HBCK, etc).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-14763) Remove usages of deprecated HConnection

2016-01-09 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-14763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15090845#comment-15090845
 ] 

Hadoop QA commented on HBASE-14763:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s 
{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m 
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s 
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m 
0s {color} | {color:green} The patch appears to include 25 new or modified test 
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m 
33s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 13s 
{color} | {color:green} master passed with JDK v1.8.0_66 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 21s 
{color} | {color:green} master passed with JDK v1.7.0_91 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 7m 
15s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m 
52s {color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 0m 58s 
{color} | {color:red} hbase-client in master has 13 extant Findbugs warnings. 
{color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 0m 44s 
{color} | {color:red} hbase-common in master has 14 extant Findbugs warnings. 
{color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 0m 12s 
{color} | {color:red} branch/hbase-it no findbugs output file 
(hbase-it/target/findbugsXml.xml) {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 1m 50s 
{color} | {color:red} hbase-server in master has 85 extant Findbugs warnings. 
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 58s 
{color} | {color:green} master passed with JDK v1.8.0_66 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 16s 
{color} | {color:green} master passed with JDK v1.7.0_91 {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red} 0m 26s 
{color} | {color:red} hbase-server in the patch failed. {color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red} 0m 22s 
{color} | {color:red} hbase-server in the patch failed with JDK v1.8.0_66. 
{color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red} 0m 22s {color} 
| {color:red} hbase-server in the patch failed with JDK v1.8.0_66. {color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red} 0m 26s 
{color} | {color:red} hbase-server in the patch failed with JDK v1.7.0_91. 
{color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red} 0m 26s {color} 
| {color:red} hbase-server in the patch failed with JDK v1.7.0_91. {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 1m 57s 
{color} | {color:red} Patch generated 1 new checkstyle issues in hbase-client 
(total was 308, now 309). {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 4m 23s 
{color} | {color:red} Patch generated 11 new checkstyle issues in hbase-server 
(total was 511, now 512). {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m 
52s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m 51s 
{color} | {color:red} Patch causes 17 errors with Hadoop v2.4.0. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 1m 43s 
{color} | {color:red} Patch causes 17 errors with Hadoop v2.4.1. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 2m 35s 
{color} | {color:red} Patch causes 17 errors with Hadoop v2.5.0. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 3m 27s 
{color} | {color:red} Patch causes 17 errors with Hadoop v2.5.1. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 4m 19s 
{color} | {color:red} Patch causes 17 errors with Hadoop v2.5.2. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 5m 11s 
{color} | {color:red} Patch causes 17 errors with Hadoop v2.6.1. {color} |
| 

[jira] [Updated] (HBASE-14763) Remove usages of deprecated HConnection

2016-01-09 Thread Jonathan Hsieh (JIRA)

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

Jonathan Hsieh updated HBASE-14763:
---
Attachment: hbase-14763.v7.patch

v7 should fix compile problems.

> Remove usages of deprecated HConnection 
> 
>
> Key: HBASE-14763
> URL: https://issues.apache.org/jira/browse/HBASE-14763
> Project: HBase
>  Issue Type: Bug
>  Components: hbase
>Affects Versions: 2.0.0
>Reporter: Jonathan Hsieh
>Assignee: Jonathan Hsieh
> Fix For: 2.0.0
>
> Attachments: hbase-14763.patch, hbase-14763.v2.patch, 
> hbase-14763.v3.patch, hbase-14763.v3.patch, hbase-14763.v4.patch, 
> hbase-14763.v5.patch, hbase-14763.v6.patch, hbase-14763.v7.patch
>
>
> HConnection was deprecated in 1.0.0.  There are two interfaces that are 
> supposed to be used instead -- Connection for client programs and 
> ClusterConnection for internal hbaes and special tools (LoadIncremental, 
> HBCK, etc).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-15087) Fix hbase-common findbugs complaints

2016-01-09 Thread Jonathan Hsieh (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-15087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15090865#comment-15090865
 ] 

Jonathan Hsieh commented on HBASE-15087:


 lgtm if bot is happy.  I kicked the bot to try the patch.

> Fix hbase-common findbugs complaints
> 
>
> Key: HBASE-15087
> URL: https://issues.apache.org/jira/browse/HBASE-15087
> Project: HBase
>  Issue Type: Sub-task
>  Components: build
>Reporter: stack
>Assignee: Stack
> Attachments: 15087.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-15087) Fix hbase-common findbugs complaints

2016-01-09 Thread Jonathan Hsieh (JIRA)

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

Jonathan Hsieh updated HBASE-15087:
---
Assignee: Stack
  Status: Patch Available  (was: Open)

> Fix hbase-common findbugs complaints
> 
>
> Key: HBASE-15087
> URL: https://issues.apache.org/jira/browse/HBASE-15087
> Project: HBase
>  Issue Type: Sub-task
>  Components: build
>Reporter: stack
>Assignee: Stack
> Attachments: 15087.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-14962) TestSplitWalDataLoss fails on all branches

2016-01-09 Thread Elliott Clark (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-14962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15090888#comment-15090888
 ] 

Elliott Clark commented on HBASE-14962:
---

If you run ./dev-support/test-util.sh -c -n 10 -u TestSplitLogManager do you 
not see the failure before completing?
I see it on mac an linux. Tried 1.7 and 1.8 on Mac. 1.8 on Linux.

> TestSplitWalDataLoss fails on all branches
> --
>
> Key: HBASE-14962
> URL: https://issues.apache.org/jira/browse/HBASE-14962
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Elliott Clark
>Assignee: stack
>Priority: Blocker
> Fix For: 1.2.0
>
>
> With some regularity I am seeing: 
> {code}
> org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: Failed 1 
> action: TestSplitWalDataLoss:dataloss: 1 time, 
>   at 
> org.apache.hadoop.hbase.client.AsyncProcess$BatchErrors.makeException(AsyncProcess.java:228)
>   at 
> org.apache.hadoop.hbase.client.AsyncProcess$BatchErrors.access$1800(AsyncProcess.java:208)
>   at 
> org.apache.hadoop.hbase.client.AsyncProcess.waitForAllPreviousOpsAndReset(AsyncProcess.java:1712)
>   at 
> org.apache.hadoop.hbase.client.BufferedMutatorImpl.backgroundFlushCommits(BufferedMutatorImpl.java:240)
>   at 
> org.apache.hadoop.hbase.client.BufferedMutatorImpl.flush(BufferedMutatorImpl.java:190)
>   at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:1430)
>   at org.apache.hadoop.hbase.client.HTable.put(HTable.java:1021)
>   at 
> org.apache.hadoop.hbase.regionserver.TestSplitWalDataLoss.test(TestSplitWalDataLoss.java:121)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Comment Edited] (HBASE-14962) TestSplitWalDataLoss fails on all branches

2016-01-09 Thread Elliott Clark (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-14962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15090888#comment-15090888
 ] 

Elliott Clark edited comment on HBASE-14962 at 1/10/16 4:48 AM:


If you run ./dev-support/test-util.sh -c -n 10 -u TestSplitLogManager do you 
not see a failure before completing?
I see it on mac an linux. Tried 1.7 and 1.8 on Mac. 1.8 on Linux.


was (Author: eclark):
If you run ./dev-support/test-util.sh -c -n 10 -u TestSplitLogManager do you 
not see the failure before completing?
I see it on mac an linux. Tried 1.7 and 1.8 on Mac. 1.8 on Linux.

> TestSplitWalDataLoss fails on all branches
> --
>
> Key: HBASE-14962
> URL: https://issues.apache.org/jira/browse/HBASE-14962
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Elliott Clark
>Assignee: stack
>Priority: Blocker
> Fix For: 1.2.0
>
>
> With some regularity I am seeing: 
> {code}
> org.apache.hadoop.hbase.client.RetriesExhaustedWithDetailsException: Failed 1 
> action: TestSplitWalDataLoss:dataloss: 1 time, 
>   at 
> org.apache.hadoop.hbase.client.AsyncProcess$BatchErrors.makeException(AsyncProcess.java:228)
>   at 
> org.apache.hadoop.hbase.client.AsyncProcess$BatchErrors.access$1800(AsyncProcess.java:208)
>   at 
> org.apache.hadoop.hbase.client.AsyncProcess.waitForAllPreviousOpsAndReset(AsyncProcess.java:1712)
>   at 
> org.apache.hadoop.hbase.client.BufferedMutatorImpl.backgroundFlushCommits(BufferedMutatorImpl.java:240)
>   at 
> org.apache.hadoop.hbase.client.BufferedMutatorImpl.flush(BufferedMutatorImpl.java:190)
>   at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:1430)
>   at org.apache.hadoop.hbase.client.HTable.put(HTable.java:1021)
>   at 
> org.apache.hadoop.hbase.regionserver.TestSplitWalDataLoss.test(TestSplitWalDataLoss.java:121)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-15082) Fix merge of MVCC and SequenceID performance regression

2016-01-09 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-15082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15090897#comment-15090897
 ] 

Hadoop QA commented on HBASE-15082:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | {color:red} docker {color} | {color:red} 8m 14s 
{color} | {color:red} Docker failed to build yetus/hbase:date2016-01-10. 
{color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12781414/15082v2.patch |
| JIRA Issue | HBASE-15082 |
| Powered by | Apache Yetus 0.1.0   http://yetus.apache.org |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/45/console |


This message was automatically generated.



> Fix merge of MVCC and SequenceID performance regression
> ---
>
> Key: HBASE-15082
> URL: https://issues.apache.org/jira/browse/HBASE-15082
> Project: HBase
>  Issue Type: Sub-task
>  Components: Performance
>Reporter: stack
>Assignee: stack
>Priority: Critical
> Fix For: 2.0.0, 1.2.0, 1.3.0
>
> Attachments: 15082.patch, 15082v2.patch, 15082v2.txt, 15082v3.txt, 
> 15082v4.patch, 15082v5.patch
>
>
> This is general fix for increments (appends, checkAnd*) perf-regression 
> identified in the parent issue. HBASE-15031 has a narrow fix for branch-1.1 
> and branch-1.0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-15082) Fix merge of MVCC and SequenceID performance regression

2016-01-09 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-15082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15090905#comment-15090905
 ] 

Hadoop QA commented on HBASE-15082:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | {color:red} docker {color} | {color:red} 3m 17s 
{color} | {color:red} Docker failed to build yetus/hbase:date2016-01-10. 
{color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12781414/15082v2.patch |
| JIRA Issue | HBASE-15082 |
| Powered by | Apache Yetus 0.1.0   http://yetus.apache.org |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/47/console |


This message was automatically generated.



> Fix merge of MVCC and SequenceID performance regression
> ---
>
> Key: HBASE-15082
> URL: https://issues.apache.org/jira/browse/HBASE-15082
> Project: HBase
>  Issue Type: Sub-task
>  Components: Performance
>Reporter: stack
>Assignee: stack
>Priority: Critical
> Fix For: 2.0.0, 1.2.0, 1.3.0
>
> Attachments: 15082.patch, 15082v2.patch, 15082v2.txt, 15082v3.txt, 
> 15082v4.patch, 15082v5.patch
>
>
> This is general fix for increments (appends, checkAnd*) perf-regression 
> identified in the parent issue. HBASE-15031 has a narrow fix for branch-1.1 
> and branch-1.0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-15087) Fix hbase-common findbugs complaints

2016-01-09 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-15087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15090910#comment-15090910
 ] 

Hadoop QA commented on HBASE-15087:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s 
{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m 
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s 
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m 0s 
{color} | {color:red} The patch doesn't appear to include any new or modified 
tests. Please justify why no new tests are needed for this patch. Also please 
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m 
45s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 20s 
{color} | {color:green} master passed with JDK v1.8.0_66 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 18s 
{color} | {color:green} master passed with JDK v1.7.0_91 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m 
7s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m 
10s {color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 0m 50s 
{color} | {color:red} hbase-common in master has 14 extant Findbugs warnings. 
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 21s 
{color} | {color:green} master passed with JDK v1.8.0_66 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 19s 
{color} | {color:green} master passed with JDK v1.7.0_91 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m 
19s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 20s 
{color} | {color:green} the patch passed with JDK v1.8.0_66 {color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red} 2m 11s {color} 
| {color:red} hbase-common-jdk1.8.0_66 with JDK v1.8.0_66 generated 15 new 
issues (was 25, now 25). {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 20s 
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 19s 
{color} | {color:green} the patch passed with JDK v1.7.0_91 {color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red} 2m 30s {color} 
| {color:red} hbase-common-jdk1.7.0_91 with JDK v1.7.0_91 generated 15 new 
issues (was 25, now 25). {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 19s 
{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 1m 11s 
{color} | {color:red} Patch generated 3 new checkstyle issues in hbase-common 
(total was 195, now 198). {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m 
11s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
24m 49s {color} | {color:green} Patch does not cause any errors with Hadoop 
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 1s 
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 23s 
{color} | {color:green} the patch passed with JDK v1.8.0_66 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 20s 
{color} | {color:green} the patch passed with JDK v1.7.0_91 {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 1m 54s 
{color} | {color:green} hbase-common in the patch passed with JDK v1.8.0_66. 
{color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 1m 50s 
{color} | {color:green} hbase-common in the patch passed with JDK v1.7.0_91. 
{color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 
8s {color} | {color:green} Patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 

[jira] [Commented] (HBASE-15082) Fix merge of MVCC and SequenceID performance regression

2016-01-09 Thread stack (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-15082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15090918#comment-15090918
 ] 

stack commented on HBASE-15082:
---

Docker failed to install spellcheck (it must know who is writing the patch if 
it is pulling that package)

[1 of 1] Compiling Main ( 
/tmp/ShellCheck-0.4.2-8/ShellCheck-0.4.2/Setup.hs, 
/tmp/ShellCheck-0.4.2-8/ShellCheck-0.4.2/dist/setup/Main.o )

/tmp/ShellCheck-0.4.2-8/ShellCheck-0.4.2/Setup.hs:15:25:
    Module `System.Process' does not export 
`callCommand'
Failed to install ShellCheck-0.4.2
cabal: Error: some packages failed to install:
ShellCheck-0.4.2 failed during the configure step. The exception was:
ExitFailure 1
The command '/bin/sh -c cabal update && cabal install shellcheck --global' 
returned a non-zero code: 1

Let me retry. See if transitory.

FYI [~busbey]

> Fix merge of MVCC and SequenceID performance regression
> ---
>
> Key: HBASE-15082
> URL: https://issues.apache.org/jira/browse/HBASE-15082
> Project: HBase
>  Issue Type: Sub-task
>  Components: Performance
>Reporter: stack
>Assignee: stack
>Priority: Critical
> Fix For: 2.0.0, 1.2.0, 1.3.0
>
> Attachments: 15082.patch, 15082v2.patch, 15082v2.txt, 15082v3.txt, 
> 15082v4.patch, 15082v5.patch
>
>
> This is general fix for increments (appends, checkAnd*) perf-regression 
> identified in the parent issue. HBASE-15031 has a narrow fix for branch-1.1 
> and branch-1.0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-15082) Fix merge of MVCC and SequenceID performance regression

2016-01-09 Thread stack (JIRA)

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

stack updated HBASE-15082:
--
Attachment: 15082v6.patch

> Fix merge of MVCC and SequenceID performance regression
> ---
>
> Key: HBASE-15082
> URL: https://issues.apache.org/jira/browse/HBASE-15082
> Project: HBase
>  Issue Type: Sub-task
>  Components: Performance
>Reporter: stack
>Assignee: stack
>Priority: Critical
> Fix For: 2.0.0, 1.2.0, 1.3.0
>
> Attachments: 15082.patch, 15082v2.patch, 15082v2.txt, 15082v3.txt, 
> 15082v4.patch, 15082v5.patch, 15082v6.patch
>
>
> This is general fix for increments (appends, checkAnd*) perf-regression 
> identified in the parent issue. HBASE-15031 has a narrow fix for branch-1.1 
> and branch-1.0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-15087) Fix hbase-common findbugs complaints

2016-01-09 Thread stack (JIRA)

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

stack updated HBASE-15087:
--
Attachment: 15087v2.patch

Fix the checkstyle errors (complaints about statement on one line).

The extant findbugs red line is about what is there currently it seems. Later 
says findbugs 'passes'.

Not sure about the javac warnings (was 25 and now is 25).

We just build hbase-common? If so, nice (Thats where changes happened).

[~busbey] if you looking out...

> Fix hbase-common findbugs complaints
> 
>
> Key: HBASE-15087
> URL: https://issues.apache.org/jira/browse/HBASE-15087
> Project: HBase
>  Issue Type: Sub-task
>  Components: build
>Reporter: stack
>Assignee: Stack
> Attachments: 15087.patch, 15087v2.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-15087) Fix hbase-common findbugs complaints

2016-01-09 Thread Sean Busbey (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-15087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15090930#comment-15090930
 ] 

Sean Busbey commented on HBASE-15087:
-

bq. Not sure about the javac warnings (was 25 and now is 25).

might be YETUS-187, or a variant of YETUS-270.

bq. We just build hbase-common? If so, nice (Thats where changes happened).

Yeah, Yetus only checks modules that have changed unless the project 
personality tells it otherwise.

> Fix hbase-common findbugs complaints
> 
>
> Key: HBASE-15087
> URL: https://issues.apache.org/jira/browse/HBASE-15087
> Project: HBase
>  Issue Type: Sub-task
>  Components: build
>Reporter: stack
>Assignee: Stack
> Attachments: 15087.patch, 15087v2.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-15082) Fix merge of MVCC and SequenceID performance regression

2016-01-09 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-15082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15090506#comment-15090506
 ] 

Hadoop QA commented on HBASE-15082:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s 
{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m 
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s 
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m 
0s {color} | {color:green} The patch appears to include 16 new or modified test 
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m 
42s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 35s 
{color} | {color:green} master passed with JDK v1.8.0_66 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 21s 
{color} | {color:green} master passed with JDK v1.7.0_91 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 7m 
30s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m 
59s {color} | {color:green} master passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 0m 58s 
{color} | {color:red} hbase-client in master has 13 extant Findbugs warnings. 
{color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 0m 42s 
{color} | {color:red} hbase-common in master has 14 extant Findbugs warnings. 
{color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 1m 54s 
{color} | {color:red} hbase-server in master has 85 extant Findbugs warnings. 
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 19s 
{color} | {color:green} master passed with JDK v1.8.0_66 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 21s 
{color} | {color:green} master passed with JDK v1.7.0_91 {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red} 0m 12s 
{color} | {color:red} hbase-examples in the patch failed. {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red} 0m 32s 
{color} | {color:red} hbase-server in the patch failed. {color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red} 0m 13s 
{color} | {color:red} hbase-examples in the patch failed with JDK v1.8.0_66. 
{color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red} 0m 34s 
{color} | {color:red} hbase-server in the patch failed with JDK v1.8.0_66. 
{color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red} 0m 13s {color} 
| {color:red} hbase-examples in the patch failed with JDK v1.8.0_66. {color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red} 0m 34s {color} 
| {color:red} hbase-server in the patch failed with JDK v1.8.0_66. {color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red} 0m 13s 
{color} | {color:red} hbase-examples in the patch failed with JDK v1.7.0_91. 
{color} |
| {color:red}-1{color} | {color:red} compile {color} | {color:red} 0m 32s 
{color} | {color:red} hbase-server in the patch failed with JDK v1.7.0_91. 
{color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red} 0m 13s {color} 
| {color:red} hbase-examples in the patch failed with JDK v1.7.0_91. {color} |
| {color:red}-1{color} | {color:red} javac {color} | {color:red} 0m 32s {color} 
| {color:red} hbase-server in the patch failed with JDK v1.7.0_91. {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 1m 4s 
{color} | {color:red} Patch generated 6 new checkstyle issues in hbase-common 
(total was 1, now 7). {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 3m 57s 
{color} | {color:red} Patch generated 66 new checkstyle issues in hbase-server 
(total was 515, now 513). {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m 
48s {color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m 1s 
{color} | {color:red} The patch has 5 line(s) that end in whitespace. Use git 
apply --whitespace=fix. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 0m 58s 
{color} | {color:red} Patch causes 14 errors with Hadoop v2.4.0. {color} |
| {color:red}-1{color} | {color:red} hadoopcheck {color} | {color:red} 1m 54s 
{color} | {color:red} Patch causes 14 errors with