[jira] [Created] (HBASE-14295) client stalling when first splitting
jvava created HBASE-14295: - Summary: client stalling when first splitting Key: HBASE-14295 URL: https://issues.apache.org/jira/browse/HBASE-14295 Project: HBase Issue Type: Bug Components: Client Affects Versions: 1.1.0.1 Environment: Linux data3 2.6.32-358.el6.x86_64 #1 SMP Fri Feb 22 00:31:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux java version 1.8.0_31 hadoop 2.6 Reporter: jvava Assignee: jvava https://issues.apache.org/jira/browse/HBASE-13942 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14293) TestStochasticBalancerJmxMetrics intermittently fails due to port conflict
[
https://issues.apache.org/jira/browse/HBASE-14293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-14293:
---
Attachment: 14293-v2.txt
TestStochasticBalancerJmxMetrics intermittently fails due to port conflict
--
Key: HBASE-14293
URL: https://issues.apache.org/jira/browse/HBASE-14293
Project: HBase
Issue Type: Test
Reporter: Ted Yu
Assignee: Ted Yu
Priority: Minor
Fix For: 2.0.0
Attachments: 14293-v1.txt, 14293-v2.txt
From
https://builds.apache.org/job/HBase-TRUNK/6748/testReport/junit/org.apache.hadoop.hbase/TestStochasticBalancerJmxMetrics/testJmxMetrics_EnsembleMode/
:
{code}
2015-08-22 20:46:07,939 ERROR [M:0;asf900:59022]
coprocessor.CoprocessorHost(518): The coprocessor
org.apache.hadoop.hbase.JMXListener threw java.rmi.server.ExportException:
Port already in use: 61120; nested exception is:
java.net.BindException: Address already in use
java.rmi.server.ExportException: Port already in use: 61120; nested exception
is:
java.net.BindException: Address already in use
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:329)
at
sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:237)
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:411)
...
2015-08-22 20:49:41,755 DEBUG [main]
hbase.TestStochasticBalancerJmxMetrics(93): Encountered exception when
starting cluster. Trying port 61122
java.lang.IllegalStateException: A mini-cluster is already running
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:981)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:872)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:866)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:810)
at
org.apache.hadoop.hbase.TestStochasticBalancerJmxMetrics.setupBeforeClass(TestStochasticBalancerJmxMetrics.java:89)
{code}
When port conflict is detected, we try the next port.
However, HTU#miniClusterRunning is true by this moment, leading to the second
exception shown above.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14293) TestStochasticBalancerJmxMetrics intermittently fails due to port conflict
[
https://issues.apache.org/jira/browse/HBASE-14293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14708504#comment-14708504
]
Lei Chen commented on HBASE-14293:
--
Forgot the link to the function:
[here|http://svn.apache.org/viewvc/camel/trunk/components/camel-test/src/main/java/org/apache/camel/test/AvailablePortFinder.java?view=markup#l130]
TestStochasticBalancerJmxMetrics intermittently fails due to port conflict
--
Key: HBASE-14293
URL: https://issues.apache.org/jira/browse/HBASE-14293
Project: HBase
Issue Type: Test
Reporter: Ted Yu
Assignee: Ted Yu
Priority: Minor
Fix For: 2.0.0
Attachments: 14293-v1.txt, 14293-v2.txt
From
https://builds.apache.org/job/HBase-TRUNK/6748/testReport/junit/org.apache.hadoop.hbase/TestStochasticBalancerJmxMetrics/testJmxMetrics_EnsembleMode/
:
{code}
2015-08-22 20:46:07,939 ERROR [M:0;asf900:59022]
coprocessor.CoprocessorHost(518): The coprocessor
org.apache.hadoop.hbase.JMXListener threw java.rmi.server.ExportException:
Port already in use: 61120; nested exception is:
java.net.BindException: Address already in use
java.rmi.server.ExportException: Port already in use: 61120; nested exception
is:
java.net.BindException: Address already in use
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:329)
at
sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:237)
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:411)
...
2015-08-22 20:49:41,755 DEBUG [main]
hbase.TestStochasticBalancerJmxMetrics(93): Encountered exception when
starting cluster. Trying port 61122
java.lang.IllegalStateException: A mini-cluster is already running
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:981)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:872)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:866)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:810)
at
org.apache.hadoop.hbase.TestStochasticBalancerJmxMetrics.setupBeforeClass(TestStochasticBalancerJmxMetrics.java:89)
{code}
When port conflict is detected, we try the next port.
However, HTU#miniClusterRunning is true by this moment, leading to the second
exception shown above.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14293) TestStochasticBalancerJmxMetrics intermittently fails due to port conflict
[
https://issues.apache.org/jira/browse/HBASE-14293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14708502#comment-14708502
]
Lei Chen commented on HBASE-14293:
--
For patch v1, it looks good.
I'm also thinking if shutting down and restart miniCluster is somehow costly,
it might be better if we can pick an available port before starting the
miniCluster? Using a function like this
Maybe randomly choose a port, and test it. If it is available, start the
miniCluster, otherwise try 10 more other random ports.
What do you think?
TestStochasticBalancerJmxMetrics intermittently fails due to port conflict
--
Key: HBASE-14293
URL: https://issues.apache.org/jira/browse/HBASE-14293
Project: HBase
Issue Type: Test
Reporter: Ted Yu
Assignee: Ted Yu
Priority: Minor
Fix For: 2.0.0
Attachments: 14293-v1.txt, 14293-v2.txt
From
https://builds.apache.org/job/HBase-TRUNK/6748/testReport/junit/org.apache.hadoop.hbase/TestStochasticBalancerJmxMetrics/testJmxMetrics_EnsembleMode/
:
{code}
2015-08-22 20:46:07,939 ERROR [M:0;asf900:59022]
coprocessor.CoprocessorHost(518): The coprocessor
org.apache.hadoop.hbase.JMXListener threw java.rmi.server.ExportException:
Port already in use: 61120; nested exception is:
java.net.BindException: Address already in use
java.rmi.server.ExportException: Port already in use: 61120; nested exception
is:
java.net.BindException: Address already in use
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:329)
at
sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:237)
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:411)
...
2015-08-22 20:49:41,755 DEBUG [main]
hbase.TestStochasticBalancerJmxMetrics(93): Encountered exception when
starting cluster. Trying port 61122
java.lang.IllegalStateException: A mini-cluster is already running
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:981)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:872)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:866)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:810)
at
org.apache.hadoop.hbase.TestStochasticBalancerJmxMetrics.setupBeforeClass(TestStochasticBalancerJmxMetrics.java:89)
{code}
When port conflict is detected, we try the next port.
However, HTU#miniClusterRunning is true by this moment, leading to the second
exception shown above.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14293) TestStochasticBalancerJmxMetrics intermittently fails due to port conflict
[
https://issues.apache.org/jira/browse/HBASE-14293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14708520#comment-14708520
]
Lei Chen commented on HBASE-14293:
--
For patch v2:
1. It seems the do-while loop will infinitely try to obtain an available port.
If there exists some extreme condition (e.g. network interface problems?) will
the loop stuck or JUnit will trigger a timeout?
2. nit, if the for loop is to try different ports, after using the port-finding
function, is it still needed?
TestStochasticBalancerJmxMetrics intermittently fails due to port conflict
--
Key: HBASE-14293
URL: https://issues.apache.org/jira/browse/HBASE-14293
Project: HBase
Issue Type: Test
Reporter: Ted Yu
Assignee: Ted Yu
Priority: Minor
Fix For: 2.0.0
Attachments: 14293-v1.txt, 14293-v2.txt
From
https://builds.apache.org/job/HBase-TRUNK/6748/testReport/junit/org.apache.hadoop.hbase/TestStochasticBalancerJmxMetrics/testJmxMetrics_EnsembleMode/
:
{code}
2015-08-22 20:46:07,939 ERROR [M:0;asf900:59022]
coprocessor.CoprocessorHost(518): The coprocessor
org.apache.hadoop.hbase.JMXListener threw java.rmi.server.ExportException:
Port already in use: 61120; nested exception is:
java.net.BindException: Address already in use
java.rmi.server.ExportException: Port already in use: 61120; nested exception
is:
java.net.BindException: Address already in use
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:329)
at
sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:237)
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:411)
...
2015-08-22 20:49:41,755 DEBUG [main]
hbase.TestStochasticBalancerJmxMetrics(93): Encountered exception when
starting cluster. Trying port 61122
java.lang.IllegalStateException: A mini-cluster is already running
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:981)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:872)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:866)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:810)
at
org.apache.hadoop.hbase.TestStochasticBalancerJmxMetrics.setupBeforeClass(TestStochasticBalancerJmxMetrics.java:89)
{code}
When port conflict is detected, we try the next port.
However, HTU#miniClusterRunning is true by this moment, leading to the second
exception shown above.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-14294) Add new attribute to Scan to limit the return size of records
[ https://issues.apache.org/jira/browse/HBASE-14294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick.han updated HBASE-14294: - Attachment: 14294-v1.patch Add new attribute to Scan to limit the return size of records - Key: HBASE-14294 URL: https://issues.apache.org/jira/browse/HBASE-14294 Project: HBase Issue Type: Improvement Affects Versions: 2.0.0 Reporter: Nick.han Assignee: Nick.han Priority: Minor Fix For: 2.0.0 Attachments: 14294-v1.patch Reason: we all use PageFilter to limit the size of the return records,but the PageFilter return limit * region number size of limit ,which is bad for a huge number of region per table. Solution: ClientScanner has a attribute caching which determine the return size of record per RPC,so we can use this attribute to limit the return size of hbase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14295) client stalling when splitting
[ https://issues.apache.org/jira/browse/HBASE-14295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jvava updated HBASE-14295: -- Summary: client stalling when splitting (was: client stalling when first splitting) client stalling when splitting -- Key: HBASE-14295 URL: https://issues.apache.org/jira/browse/HBASE-14295 Project: HBase Issue Type: Bug Components: Client Affects Versions: 1.1.0.1 Environment: Linux data3 2.6.32-358.el6.x86_64 #1 SMP Fri Feb 22 00:31:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux java version 1.8.0_31 hadoop 2.6 Reporter: jvava Assignee: jvava Labels: easytest https://issues.apache.org/jira/browse/HBASE-13942 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13408) HBase In-Memory Memstore Compaction
[ https://issues.apache.org/jira/browse/HBASE-13408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14708312#comment-14708312 ] Edward Bortnikov commented on HBASE-13408: -- [~mbertozzi] we absolutely agree that there is a room for more optimizations. We strived to demonstrate a minimum viable implementation, and this is already a big patch. The published performance results show benefits for both random access and scan patterns, for a variety of data distributions. Admittedly, we were more after speed than memory optimization. Re/ the concrete questions: 1. HFile implementation for memstore segments. Very plausible (in fact, the internal API's allow to plug in this implementation quite easily). 2. Automatic memstore compaction (not only in-memory families). Our thinking was to let the system administrator remain in control of what is happening, so we introduced this limitation. Could be relaxed in the future. Thanks for all the feedback. We are open to discussion and adjustments that would eventually lead this feature to HBase mainstream. HBase In-Memory Memstore Compaction --- Key: HBASE-13408 URL: https://issues.apache.org/jira/browse/HBASE-13408 Project: HBase Issue Type: New Feature Reporter: Eshcar Hillel Attachments: HBASE-13408-trunk-v01.patch, HBASE-13408-trunk-v02.patch, HBaseIn-MemoryMemstoreCompactionDesignDocument-ver02.pdf, HBaseIn-MemoryMemstoreCompactionDesignDocument.pdf, InMemoryMemstoreCompactionEvaluationResults.pdf, InMemoryMemstoreCompactionScansEvaluationResults.pdf A store unit holds a column family in a region, where the memstore is its in-memory component. The memstore absorbs all updates to the store; from time to time these updates are flushed to a file on disk, where they are compacted. Unlike disk components, the memstore is not compacted until it is written to the filesystem and optionally to block-cache. This may result in underutilization of the memory due to duplicate entries per row, for example, when hot data is continuously updated. Generally, the faster the data is accumulated in memory, more flushes are triggered, the data sinks to disk more frequently, slowing down retrieval of data, even if very recent. In high-churn workloads, compacting the memstore can help maintain the data in memory, and thereby speed up data retrieval. We suggest a new compacted memstore with the following principles: 1.The data is kept in memory for as long as possible 2.Memstore data is either compacted or in process of being compacted 3.Allow a panic mode, which may interrupt an in-progress compaction and force a flush of part of the memstore. We suggest applying this optimization only to in-memory column families. A design document is attached. This feature was previously discussed in HBASE-5311. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14273) Rename MVCC to MVCC: From MultiVersionConsistencyControl to MultiVersionConcurrencyControl
[ https://issues.apache.org/jira/browse/HBASE-14273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14708343#comment-14708343 ] Lars Francke commented on HBASE-14273: -- I can provide a patch for branch-1 if you want me to. The test failures seem unrelated to me. Rename MVCC to MVCC: From MultiVersionConsistencyControl to MultiVersionConcurrencyControl -- Key: HBASE-14273 URL: https://issues.apache.org/jira/browse/HBASE-14273 Project: HBase Issue Type: Bug Reporter: stack Assignee: Lars Francke Labels: beginner Attachments: HBASE-14273.patch [~larsgeorge] noticed that our MVCC class has Consistency as the first 'C' when it should be 'Concurrency'. The issue that named this class, HBASE-4544 talks about 'Concurrency' but then it went in as Consistency (Why has no one noticed this before now? Thanks [~larsgeorge]) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13696) Prune retired hbase versions from ref guide prereq support tables
[ https://issues.apache.org/jira/browse/HBASE-13696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Liptak updated HBASE-13696: - Attachment: HBASE-13696.1.patch [~busbey] This is wider scope, removing references to versions below 0.98 (earliest supported). I didn't modify some developer sections (like How to set fix version in JIRA on issue resolve) and the history section. Prune retired hbase versions from ref guide prereq support tables - Key: HBASE-13696 URL: https://issues.apache.org/jira/browse/HBASE-13696 Project: HBase Issue Type: Task Reporter: Sean Busbey Labels: beginner Attachments: HBASE-13696.1.patch the java table still contains HBase 0.96, and the Hadoop table still has HBase 0.92 and 0.96. We should remove these. Their details can still be found in their last release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14277) TestRegionServerHostname.testRegionServerHostname may fail at host with a case sensitive name
[ https://issues.apache.org/jira/browse/HBASE-14277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liu Shaohui updated HBASE-14277: Fix Version/s: 1.1.3 1.0.3 1.2.1 0.98.15 TestRegionServerHostname.testRegionServerHostname may fail at host with a case sensitive name - Key: HBASE-14277 URL: https://issues.apache.org/jira/browse/HBASE-14277 Project: HBase Issue Type: Test Components: test Affects Versions: 2.0.0 Reporter: Liu Shaohui Assignee: Liu Shaohui Priority: Minor Fix For: 2.0.0, 0.98.15, 1.2.1, 1.0.3, 1.1.3 Attachments: HBASE-14277-v001.diff, HBASE-14277-v002.diff After HBASE-13995, hostname will be converted to lower case in ServerName. It may cause the test: TestRegionServerHostname.testRegionServerHostname failed at host with a case sensitive name. Just fix it in test. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14293) TestStochasticBalancerJmxMetrics intermittently fails due to port conflict
[
https://issues.apache.org/jira/browse/HBASE-14293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated HBASE-14293:
---
Attachment: 14293-v3.txt
For #1, if network has problem, there is not much we can do - the mini cluster
wouldn't start, not just for this test.
For #2, the loop is still necessary since HTU#available() only checks one port.
Patch v3 oscillates the ports being searched on both sides of the initial port.
TestStochasticBalancerJmxMetrics intermittently fails due to port conflict
--
Key: HBASE-14293
URL: https://issues.apache.org/jira/browse/HBASE-14293
Project: HBase
Issue Type: Test
Reporter: Ted Yu
Assignee: Ted Yu
Priority: Minor
Fix For: 2.0.0
Attachments: 14293-v1.txt, 14293-v2.txt, 14293-v3.txt
From
https://builds.apache.org/job/HBase-TRUNK/6748/testReport/junit/org.apache.hadoop.hbase/TestStochasticBalancerJmxMetrics/testJmxMetrics_EnsembleMode/
:
{code}
2015-08-22 20:46:07,939 ERROR [M:0;asf900:59022]
coprocessor.CoprocessorHost(518): The coprocessor
org.apache.hadoop.hbase.JMXListener threw java.rmi.server.ExportException:
Port already in use: 61120; nested exception is:
java.net.BindException: Address already in use
java.rmi.server.ExportException: Port already in use: 61120; nested exception
is:
java.net.BindException: Address already in use
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:329)
at
sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:237)
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:411)
...
2015-08-22 20:49:41,755 DEBUG [main]
hbase.TestStochasticBalancerJmxMetrics(93): Encountered exception when
starting cluster. Trying port 61122
java.lang.IllegalStateException: A mini-cluster is already running
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:981)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:872)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:866)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:810)
at
org.apache.hadoop.hbase.TestStochasticBalancerJmxMetrics.setupBeforeClass(TestStochasticBalancerJmxMetrics.java:89)
{code}
When port conflict is detected, we try the next port.
However, HTU#miniClusterRunning is true by this moment, leading to the second
exception shown above.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (HBASE-14281) ArrayIndexOutOfBoundsException in CellComparator#getMinimumMidpointArray, part 2
[ https://issues.apache.org/jira/browse/HBASE-14281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl reassigned HBASE-14281: - Assignee: Lars Hofhansl (was: Michael Rose) ArrayIndexOutOfBoundsException in CellComparator#getMinimumMidpointArray, part 2 Key: HBASE-14281 URL: https://issues.apache.org/jira/browse/HBASE-14281 Project: HBase Issue Type: Bug Components: regionserver Affects Versions: 1.0.0, 1.0.1, 1.0.2 Reporter: Michael Rose Assignee: Lars Hofhansl Attachments: 14281-v1.patch Follow-on issue for HBASE-13329: CellComparator#getMinimumMidpointArray seems to have had a necessary change omitted and the patch only covered one of the two places diffIdx could overflow the short. For some background, we ran into the HBASE-13329 issue where a flush would cause a regionserver abort. After abort, the region in question would almost indefinitely sit in the FAILED_OPEN state. Applying the patch from HBASE-13329 didn't solve the issue, but I noticed a comment in that issue which applied the same change in CellComparator#getMinimumMidpointArray, but the change was omitted from the attached patch. RS abort for reference: slave3.xxx.xxx.xxx,60020,1440131603772: Replay of WAL required. Forcing server shutdown org.apache.hadoop.hbase.DroppedSnapshotException: region: deduplication,P\xDFt\x10\x053e73ceff5a2717d2ba76887ea21a2a8e353d1372\xFE,1438362391124.2bb6a602be6b1bfcea0508af4ba42235. at org.apache.hadoop.hbase.regionserver.HRegion.internalFlushCacheAndCommit(HRegion.java:2243) at org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:1972) at org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:1935) at org.apache.hadoop.hbase.regionserver.HRegion.flushcache(HRegion.java:1833) at org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:452) at org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:413) at org.apache.hadoop.hbase.regionserver.MemStoreFlusher.access$800(MemStoreFlusher.java:70) at org.apache.hadoop.hbase.regionserver.MemStoreFlusher$FlushHandler.run(MemStoreFlusher.java:229) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NegativeArraySizeException at org.apache.hadoop.hbase.CellComparator.getMinimumMidpointArray(CellComparator.java:494) at org.apache.hadoop.hbase.CellComparator.getMidpoint(CellComparator.java:448) at org.apache.hadoop.hbase.io.hfile.HFileWriterV2.finishBlock(HFileWriterV2.java:165) at org.apache.hadoop.hbase.io.hfile.HFileWriterV2.checkBlockBoundary(HFileWriterV2.java:146) at org.apache.hadoop.hbase.io.hfile.HFileWriterV2.append(HFileWriterV2.java:263) at org.apache.hadoop.hbase.regionserver.StoreFile$Writer.append(StoreFile.java:949) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14281) ArrayIndexOutOfBoundsException in CellComparator#getMinimumMidpointArray, part 2
[ https://issues.apache.org/jira/browse/HBASE-14281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14708575#comment-14708575 ] Lars Hofhansl commented on HBASE-14281: --- This is the same stack track as in HBASE-13329. Did that change get reverted somehow? ArrayIndexOutOfBoundsException in CellComparator#getMinimumMidpointArray, part 2 Key: HBASE-14281 URL: https://issues.apache.org/jira/browse/HBASE-14281 Project: HBase Issue Type: Bug Components: regionserver Affects Versions: 1.0.0, 1.0.1, 1.0.2 Reporter: Michael Rose Assignee: Lars Hofhansl Attachments: 14281-v1.patch Follow-on issue for HBASE-13329: CellComparator#getMinimumMidpointArray seems to have had a necessary change omitted and the patch only covered one of the two places diffIdx could overflow the short. For some background, we ran into the HBASE-13329 issue where a flush would cause a regionserver abort. After abort, the region in question would almost indefinitely sit in the FAILED_OPEN state. Applying the patch from HBASE-13329 didn't solve the issue, but I noticed a comment in that issue which applied the same change in CellComparator#getMinimumMidpointArray, but the change was omitted from the attached patch. RS abort for reference: slave3.xxx.xxx.xxx,60020,1440131603772: Replay of WAL required. Forcing server shutdown org.apache.hadoop.hbase.DroppedSnapshotException: region: deduplication,P\xDFt\x10\x053e73ceff5a2717d2ba76887ea21a2a8e353d1372\xFE,1438362391124.2bb6a602be6b1bfcea0508af4ba42235. at org.apache.hadoop.hbase.regionserver.HRegion.internalFlushCacheAndCommit(HRegion.java:2243) at org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:1972) at org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:1935) at org.apache.hadoop.hbase.regionserver.HRegion.flushcache(HRegion.java:1833) at org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:452) at org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:413) at org.apache.hadoop.hbase.regionserver.MemStoreFlusher.access$800(MemStoreFlusher.java:70) at org.apache.hadoop.hbase.regionserver.MemStoreFlusher$FlushHandler.run(MemStoreFlusher.java:229) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NegativeArraySizeException at org.apache.hadoop.hbase.CellComparator.getMinimumMidpointArray(CellComparator.java:494) at org.apache.hadoop.hbase.CellComparator.getMidpoint(CellComparator.java:448) at org.apache.hadoop.hbase.io.hfile.HFileWriterV2.finishBlock(HFileWriterV2.java:165) at org.apache.hadoop.hbase.io.hfile.HFileWriterV2.checkBlockBoundary(HFileWriterV2.java:146) at org.apache.hadoop.hbase.io.hfile.HFileWriterV2.append(HFileWriterV2.java:263) at org.apache.hadoop.hbase.regionserver.StoreFile$Writer.append(StoreFile.java:949) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13696) Prune retired hbase versions from ref guide prereq support tables
[ https://issues.apache.org/jira/browse/HBASE-13696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Liptak updated HBASE-13696: - Release Note: HBASE-13696 Cleanup references in documentation to 0.90/0.92/0.94/0.95/0.96 Status: Patch Available (was: Open) Prune retired hbase versions from ref guide prereq support tables - Key: HBASE-13696 URL: https://issues.apache.org/jira/browse/HBASE-13696 Project: HBase Issue Type: Task Reporter: Sean Busbey Labels: beginner Attachments: HBASE-13696.1.patch the java table still contains HBase 0.96, and the Hadoop table still has HBase 0.92 and 0.96. We should remove these. Their details can still be found in their last release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HBASE-13696) Prune retired hbase versions from ref guide prereq support tables
[ https://issues.apache.org/jira/browse/HBASE-13696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Liptak reassigned HBASE-13696: Assignee: Gabor Liptak Prune retired hbase versions from ref guide prereq support tables - Key: HBASE-13696 URL: https://issues.apache.org/jira/browse/HBASE-13696 Project: HBase Issue Type: Task Reporter: Sean Busbey Assignee: Gabor Liptak Labels: beginner Attachments: HBASE-13696.1.patch the java table still contains HBase 0.96, and the Hadoop table still has HBase 0.92 and 0.96. We should remove these. Their details can still be found in their last release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14281) ArrayIndexOutOfBoundsException in CellComparator#getMinimumMidpointArray, part 2
[ https://issues.apache.org/jira/browse/HBASE-14281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14708580#comment-14708580 ] Lars Hofhansl commented on HBASE-14281: --- (not sure how it got assigned to me... assigned it back to Michael) ArrayIndexOutOfBoundsException in CellComparator#getMinimumMidpointArray, part 2 Key: HBASE-14281 URL: https://issues.apache.org/jira/browse/HBASE-14281 Project: HBase Issue Type: Bug Components: regionserver Affects Versions: 1.0.0, 1.0.1, 1.0.2 Reporter: Michael Rose Assignee: Michael Rose Attachments: 14281-v1.patch Follow-on issue for HBASE-13329: CellComparator#getMinimumMidpointArray seems to have had a necessary change omitted and the patch only covered one of the two places diffIdx could overflow the short. For some background, we ran into the HBASE-13329 issue where a flush would cause a regionserver abort. After abort, the region in question would almost indefinitely sit in the FAILED_OPEN state. Applying the patch from HBASE-13329 didn't solve the issue, but I noticed a comment in that issue which applied the same change in CellComparator#getMinimumMidpointArray, but the change was omitted from the attached patch. RS abort for reference: slave3.xxx.xxx.xxx,60020,1440131603772: Replay of WAL required. Forcing server shutdown org.apache.hadoop.hbase.DroppedSnapshotException: region: deduplication,P\xDFt\x10\x053e73ceff5a2717d2ba76887ea21a2a8e353d1372\xFE,1438362391124.2bb6a602be6b1bfcea0508af4ba42235. at org.apache.hadoop.hbase.regionserver.HRegion.internalFlushCacheAndCommit(HRegion.java:2243) at org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:1972) at org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:1935) at org.apache.hadoop.hbase.regionserver.HRegion.flushcache(HRegion.java:1833) at org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:452) at org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:413) at org.apache.hadoop.hbase.regionserver.MemStoreFlusher.access$800(MemStoreFlusher.java:70) at org.apache.hadoop.hbase.regionserver.MemStoreFlusher$FlushHandler.run(MemStoreFlusher.java:229) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NegativeArraySizeException at org.apache.hadoop.hbase.CellComparator.getMinimumMidpointArray(CellComparator.java:494) at org.apache.hadoop.hbase.CellComparator.getMidpoint(CellComparator.java:448) at org.apache.hadoop.hbase.io.hfile.HFileWriterV2.finishBlock(HFileWriterV2.java:165) at org.apache.hadoop.hbase.io.hfile.HFileWriterV2.checkBlockBoundary(HFileWriterV2.java:146) at org.apache.hadoop.hbase.io.hfile.HFileWriterV2.append(HFileWriterV2.java:263) at org.apache.hadoop.hbase.regionserver.StoreFile$Writer.append(StoreFile.java:949) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14281) ArrayIndexOutOfBoundsException in CellComparator#getMinimumMidpointArray, part 2
[ https://issues.apache.org/jira/browse/HBASE-14281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-14281: -- Assignee: Michael Rose (was: Dr Mich Talebzadeh) ArrayIndexOutOfBoundsException in CellComparator#getMinimumMidpointArray, part 2 Key: HBASE-14281 URL: https://issues.apache.org/jira/browse/HBASE-14281 Project: HBase Issue Type: Bug Components: regionserver Affects Versions: 1.0.0, 1.0.1, 1.0.2 Reporter: Michael Rose Assignee: Michael Rose Attachments: 14281-v1.patch Follow-on issue for HBASE-13329: CellComparator#getMinimumMidpointArray seems to have had a necessary change omitted and the patch only covered one of the two places diffIdx could overflow the short. For some background, we ran into the HBASE-13329 issue where a flush would cause a regionserver abort. After abort, the region in question would almost indefinitely sit in the FAILED_OPEN state. Applying the patch from HBASE-13329 didn't solve the issue, but I noticed a comment in that issue which applied the same change in CellComparator#getMinimumMidpointArray, but the change was omitted from the attached patch. RS abort for reference: slave3.xxx.xxx.xxx,60020,1440131603772: Replay of WAL required. Forcing server shutdown org.apache.hadoop.hbase.DroppedSnapshotException: region: deduplication,P\xDFt\x10\x053e73ceff5a2717d2ba76887ea21a2a8e353d1372\xFE,1438362391124.2bb6a602be6b1bfcea0508af4ba42235. at org.apache.hadoop.hbase.regionserver.HRegion.internalFlushCacheAndCommit(HRegion.java:2243) at org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:1972) at org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:1935) at org.apache.hadoop.hbase.regionserver.HRegion.flushcache(HRegion.java:1833) at org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:452) at org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:413) at org.apache.hadoop.hbase.regionserver.MemStoreFlusher.access$800(MemStoreFlusher.java:70) at org.apache.hadoop.hbase.regionserver.MemStoreFlusher$FlushHandler.run(MemStoreFlusher.java:229) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NegativeArraySizeException at org.apache.hadoop.hbase.CellComparator.getMinimumMidpointArray(CellComparator.java:494) at org.apache.hadoop.hbase.CellComparator.getMidpoint(CellComparator.java:448) at org.apache.hadoop.hbase.io.hfile.HFileWriterV2.finishBlock(HFileWriterV2.java:165) at org.apache.hadoop.hbase.io.hfile.HFileWriterV2.checkBlockBoundary(HFileWriterV2.java:146) at org.apache.hadoop.hbase.io.hfile.HFileWriterV2.append(HFileWriterV2.java:263) at org.apache.hadoop.hbase.regionserver.StoreFile$Writer.append(StoreFile.java:949) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14281) ArrayIndexOutOfBoundsException in CellComparator#getMinimumMidpointArray, part 2
[ https://issues.apache.org/jira/browse/HBASE-14281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl updated HBASE-14281: -- Assignee: Dr Mich Talebzadeh (was: Lars Hofhansl) ArrayIndexOutOfBoundsException in CellComparator#getMinimumMidpointArray, part 2 Key: HBASE-14281 URL: https://issues.apache.org/jira/browse/HBASE-14281 Project: HBase Issue Type: Bug Components: regionserver Affects Versions: 1.0.0, 1.0.1, 1.0.2 Reporter: Michael Rose Assignee: Dr Mich Talebzadeh Attachments: 14281-v1.patch Follow-on issue for HBASE-13329: CellComparator#getMinimumMidpointArray seems to have had a necessary change omitted and the patch only covered one of the two places diffIdx could overflow the short. For some background, we ran into the HBASE-13329 issue where a flush would cause a regionserver abort. After abort, the region in question would almost indefinitely sit in the FAILED_OPEN state. Applying the patch from HBASE-13329 didn't solve the issue, but I noticed a comment in that issue which applied the same change in CellComparator#getMinimumMidpointArray, but the change was omitted from the attached patch. RS abort for reference: slave3.xxx.xxx.xxx,60020,1440131603772: Replay of WAL required. Forcing server shutdown org.apache.hadoop.hbase.DroppedSnapshotException: region: deduplication,P\xDFt\x10\x053e73ceff5a2717d2ba76887ea21a2a8e353d1372\xFE,1438362391124.2bb6a602be6b1bfcea0508af4ba42235. at org.apache.hadoop.hbase.regionserver.HRegion.internalFlushCacheAndCommit(HRegion.java:2243) at org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:1972) at org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:1935) at org.apache.hadoop.hbase.regionserver.HRegion.flushcache(HRegion.java:1833) at org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:452) at org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:413) at org.apache.hadoop.hbase.regionserver.MemStoreFlusher.access$800(MemStoreFlusher.java:70) at org.apache.hadoop.hbase.regionserver.MemStoreFlusher$FlushHandler.run(MemStoreFlusher.java:229) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NegativeArraySizeException at org.apache.hadoop.hbase.CellComparator.getMinimumMidpointArray(CellComparator.java:494) at org.apache.hadoop.hbase.CellComparator.getMidpoint(CellComparator.java:448) at org.apache.hadoop.hbase.io.hfile.HFileWriterV2.finishBlock(HFileWriterV2.java:165) at org.apache.hadoop.hbase.io.hfile.HFileWriterV2.checkBlockBoundary(HFileWriterV2.java:146) at org.apache.hadoop.hbase.io.hfile.HFileWriterV2.append(HFileWriterV2.java:263) at org.apache.hadoop.hbase.regionserver.StoreFile$Writer.append(StoreFile.java:949) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14281) ArrayIndexOutOfBoundsException in CellComparator#getMinimumMidpointArray, part 2
[ https://issues.apache.org/jira/browse/HBASE-14281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14708579#comment-14708579 ] Lars Hofhansl commented on HBASE-14281: --- Can somebody clean up the confusion? I checked in branch-1 and trunk and the change (HBASE-13329) is there as expected. What's missing? Did you apply the trunk patch to 1.0? The attached patch is definitely already in branch-1. Hence my confusion. ArrayIndexOutOfBoundsException in CellComparator#getMinimumMidpointArray, part 2 Key: HBASE-14281 URL: https://issues.apache.org/jira/browse/HBASE-14281 Project: HBase Issue Type: Bug Components: regionserver Affects Versions: 1.0.0, 1.0.1, 1.0.2 Reporter: Michael Rose Assignee: Lars Hofhansl Attachments: 14281-v1.patch Follow-on issue for HBASE-13329: CellComparator#getMinimumMidpointArray seems to have had a necessary change omitted and the patch only covered one of the two places diffIdx could overflow the short. For some background, we ran into the HBASE-13329 issue where a flush would cause a regionserver abort. After abort, the region in question would almost indefinitely sit in the FAILED_OPEN state. Applying the patch from HBASE-13329 didn't solve the issue, but I noticed a comment in that issue which applied the same change in CellComparator#getMinimumMidpointArray, but the change was omitted from the attached patch. RS abort for reference: slave3.xxx.xxx.xxx,60020,1440131603772: Replay of WAL required. Forcing server shutdown org.apache.hadoop.hbase.DroppedSnapshotException: region: deduplication,P\xDFt\x10\x053e73ceff5a2717d2ba76887ea21a2a8e353d1372\xFE,1438362391124.2bb6a602be6b1bfcea0508af4ba42235. at org.apache.hadoop.hbase.regionserver.HRegion.internalFlushCacheAndCommit(HRegion.java:2243) at org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:1972) at org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:1935) at org.apache.hadoop.hbase.regionserver.HRegion.flushcache(HRegion.java:1833) at org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:452) at org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:413) at org.apache.hadoop.hbase.regionserver.MemStoreFlusher.access$800(MemStoreFlusher.java:70) at org.apache.hadoop.hbase.regionserver.MemStoreFlusher$FlushHandler.run(MemStoreFlusher.java:229) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NegativeArraySizeException at org.apache.hadoop.hbase.CellComparator.getMinimumMidpointArray(CellComparator.java:494) at org.apache.hadoop.hbase.CellComparator.getMidpoint(CellComparator.java:448) at org.apache.hadoop.hbase.io.hfile.HFileWriterV2.finishBlock(HFileWriterV2.java:165) at org.apache.hadoop.hbase.io.hfile.HFileWriterV2.checkBlockBoundary(HFileWriterV2.java:146) at org.apache.hadoop.hbase.io.hfile.HFileWriterV2.append(HFileWriterV2.java:263) at org.apache.hadoop.hbase.regionserver.StoreFile$Writer.append(StoreFile.java:949) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14277) TestRegionServerHostname.testRegionServerHostname may fail at host with a case sensitive name
[ https://issues.apache.org/jira/browse/HBASE-14277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liu Shaohui updated HBASE-14277: Fix Version/s: (was: 1.1.3) (was: 1.0.3) (was: 1.2.1) (was: 0.98.15) 1.1.2 1.2.0 TestRegionServerHostname.testRegionServerHostname may fail at host with a case sensitive name - Key: HBASE-14277 URL: https://issues.apache.org/jira/browse/HBASE-14277 Project: HBase Issue Type: Test Components: test Affects Versions: 2.0.0 Reporter: Liu Shaohui Assignee: Liu Shaohui Priority: Minor Fix For: 2.0.0, 1.2.0, 1.1.2 Attachments: HBASE-14277-v001.diff, HBASE-14277-v002.diff After HBASE-13995, hostname will be converted to lower case in ServerName. It may cause the test: TestRegionServerHostname.testRegionServerHostname failed at host with a case sensitive name. Just fix it in test. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14292) Call Me Maybe HBase links haved moved
[ https://issues.apache.org/jira/browse/HBASE-14292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14708759#comment-14708759 ] Andrew Purtell commented on HBASE-14292: Thanks for letting us know [~rayokota] Call Me Maybe HBase links haved moved - Key: HBASE-14292 URL: https://issues.apache.org/jira/browse/HBASE-14292 Project: HBase Issue Type: Bug Components: documentation Reporter: Robert Yokota Assignee: Misty Stanley-Jones Priority: Minor Attachments: HBASE-14292.patch The links to the Yammer engineering blog have moved. Please use the following links in section 83.5. Network Consistency and Partition Tolerance http://old.eng.yammer.com/call-me-maybe-hbase/ http://old.eng.yammer.com/call-me-maybe-hbase-addendum/ Thanks -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14298) Source assemblies incorrect after recent POM changes (0.98)
[
https://issues.apache.org/jira/browse/HBASE-14298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-14298:
---
Attachment: HBASE-14298-0.98.patch
Updated patch that doesn't undo HBASE-14297
Source assemblies incorrect after recent POM changes (0.98)
---
Key: HBASE-14298
URL: https://issues.apache.org/jira/browse/HBASE-14298
Project: HBase
Issue Type: Bug
Affects Versions: 0.98.14
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Priority: Blocker
Fix For: 0.98.14
Attachments: HBASE-14298-0.98.patch, HBASE-14298-0.98.patch
After recent POM changes when building source assemblies:
{noformat}
$ mvn clean install -DskipTests assembly:single \
-Dassembly.file=hbase-assembly/src/main/assembly/src.xml -Prelease
{noformat}
several modules are now missing from the resulting tarball: hbase-assembly,
hbase-examples, hbase-it, hbase-resource-bundle, hbase-rest, hbase-shell,
hbase-testing-util, hbase-thrift
Here's what we should have:
{noformat}
bin
CHANGES.txt
conf
dev-support
hbase-annotations
hbase-assembly
hbase-checkstyle
hbase-client
hbase-common
hbase-examples
hbase-hadoop1-compat
hbase-hadoop2-compat
hbase-hadoop-compat
hbase-it
hbase-prefix-tree
hbase-protocol
hbase-resource-bundle
hbase-rest
hbase-server
hbase-shell
hbase-testing-util
hbase-thrift
LICENSE.txt
NOTICE.txt
pom.xml
README.txt
src
{noformat}
Here's what only shows up in the source tarball:
{noformat}
bin
CHANGES.txt
conf
dev-support
hbase-annotations
hbase-checkstyle
hbase-client
hbase-common
hbase-hadoop1-compat
hbase-hadoop2-compat
hbase-hadoop-compat
hbase-prefix-tree
hbase-protocol
hbase-resource-bundle
hbase-server
LICENSE.txt
NOTICE.txt
pom.xml
README.txt
src
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-14260) don't build javadocs for hbase-protocol module
[
https://issues.apache.org/jira/browse/HBASE-14260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-14260:
---
Fix Version/s: (was: 0.98.15)
0.98.14
don't build javadocs for hbase-protocol module
--
Key: HBASE-14260
URL: https://issues.apache.org/jira/browse/HBASE-14260
Project: HBase
Issue Type: Improvement
Affects Versions: 0.98.0, 1.0.0, 2.0.0, 1.1.0, 1.2.0
Reporter: Sean Busbey
Assignee: Sean Busbey
Fix For: 2.0.0, 0.98.14, 1.2.0, 1.1.2, 1.3.0, 1.0.3
Attachments: HBASE-14260.1.patch
I'm not sure I have all the affected versions, but it seems that something is
amiss in making our javadocs:
{code}
mvn -Papache-release -Prelease -DskipTests clean package
... SNIP ...
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache HBase ... SUCCESS [ 11.149
s]
[INFO] Apache HBase - Checkstyle .. SUCCESS [ 1.249
s]
[INFO] Apache HBase - Resource Bundle . SUCCESS [ 0.539
s]
[INFO] Apache HBase - Annotations . SUCCESS [ 4.438
s]
[INFO] Apache HBase - Protocol SUCCESS [10:15
min]
[INFO] Apache HBase - Common .. SUCCESS [ 48.465
s]
[INFO] Apache HBase - Procedure ... SUCCESS [ 14.375
s]
[INFO] Apache HBase - Client .. SUCCESS [ 45.187
s]
[INFO] Apache HBase - Hadoop Compatibility SUCCESS [ 6.998
s]
[INFO] Apache HBase - Hadoop Two Compatibility SUCCESS [ 14.891
s]
[INFO] Apache HBase - Prefix Tree . SUCCESS [ 14.214
s]
[INFO] Apache HBase - Server .. SUCCESS [02:01
min]
[INFO] Apache HBase - Testing Util SUCCESS [ 12.779
s]
[INFO] Apache HBase - Thrift .. SUCCESS [01:15
min]
[INFO] Apache HBase - Shell ... SUCCESS [ 6.649
s]
[INFO] Apache HBase - Integration Tests ... SUCCESS [ 6.429
s]
[INFO] Apache HBase - Examples SUCCESS [ 13.200
s]
[INFO] Apache HBase - Rest SUCCESS [ 27.831
s]
[INFO] Apache HBase - Assembly SUCCESS [ 19.400
s]
[INFO] Apache HBase - Shaded .. SUCCESS [ 0.419
s]
[INFO] Apache HBase - Shaded - Client . SUCCESS [ 23.707
s]
[INFO] Apache HBase - Shaded - Server . SUCCESS [ 43.654
s]
[INFO] Apache HBase - Spark ... SUCCESS [02:22
min]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 21:13 min
[INFO] Finished at: 2015-08-19T15:48:00-05:00
[INFO] Final Memory: 181M/1513M
[INFO]
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-14288) Upgrade asciidoctor plugin to v1.5.2.1
[ https://issues.apache.org/jira/browse/HBASE-14288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-14288: --- Fix Version/s: (was: 0.98.15) 0.98.14 Upgrade asciidoctor plugin to v1.5.2.1 -- Key: HBASE-14288 URL: https://issues.apache.org/jira/browse/HBASE-14288 Project: HBase Issue Type: Task Components: build Reporter: Nick Dimiduk Assignee: Nick Dimiduk Priority: Minor Fix For: 2.0.0, 0.98.14, 1.2.0, 1.1.2, 1.3.0, 1.0.3 Attachments: 0001-HBASE-14288-Upgrade-asciidoctor-plugin-to-v1.5.2.1.patch, 14288.v1.patch While debugging HBASE-14250 I learned that our version of the asciidoctor plugin (1.5.2) does not support the skip property. 1.5.2.1 does. Skipping doc generation speeds up debugging the build immensely. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14251) javadoc jars use LICENSE/NOTICE from primary artifact
[ https://issues.apache.org/jira/browse/HBASE-14251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-14251: --- Fix Version/s: (was: 0.98.15) 0.98.14 javadoc jars use LICENSE/NOTICE from primary artifact - Key: HBASE-14251 URL: https://issues.apache.org/jira/browse/HBASE-14251 Project: HBase Issue Type: Bug Components: build Affects Versions: 2.0.0, 1.2.0, 1.1.2, 0.98.15, 1.0.3 Reporter: Sean Busbey Assignee: Sean Busbey Priority: Blocker Fix For: 2.0.0, 0.98.14, 1.2.0, 1.1.2, 1.3.0, 1.0.3 Attachments: HBASE-14251.1.patch Our generated javadoc jars have the same LICENSE/NOTICE files as our primary artifacts but do not include a copy of hte full source. the following modules end up with incorrect artifacts: * hbase-server * hbase-common (maybe? depends on the are-apis-copyrightable court case) * hbase-thrift -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14250) branch-1.1 hbase-server test-jar has incorrect LICENSE
[ https://issues.apache.org/jira/browse/HBASE-14250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-14250: --- Fix Version/s: (was: 0.98.15) 0.98.14 branch-1.1 hbase-server test-jar has incorrect LICENSE -- Key: HBASE-14250 URL: https://issues.apache.org/jira/browse/HBASE-14250 Project: HBase Issue Type: Bug Components: build Affects Versions: 2.0.0, 1.2.0, 1.1.2, 1.3.0, 0.98.15, 1.0.3 Reporter: Sean Busbey Assignee: Sean Busbey Priority: Blocker Fix For: 2.0.0, 0.98.14, 1.2.0, 1.1.2, 1.3.0, 1.0.3 Attachments: HBASE-14250.1.patch, HBASE-14250_repro.sh test-jar LICENSE file for hbase-server claims jquery and the orca logo are present in the jar, when they are not. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14277) TestRegionServerHostname.testRegionServerHostname may fail at host with a case sensitive name
[ https://issues.apache.org/jira/browse/HBASE-14277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14708778#comment-14708778 ] Hudson commented on HBASE-14277: FAILURE: Integrated in HBase-1.2-IT #109 (See [https://builds.apache.org/job/HBase-1.2-IT/109/]) HBASE-14277 TestRegionServerHostname.testRegionServerHostname may fail at host with a case sensitive name (liushaohui: rev 65f1e9ebce970e991ec3c854a3ec56a5389920b7) * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestRegionServerHostname.java TestRegionServerHostname.testRegionServerHostname may fail at host with a case sensitive name - Key: HBASE-14277 URL: https://issues.apache.org/jira/browse/HBASE-14277 Project: HBase Issue Type: Test Components: test Affects Versions: 2.0.0 Reporter: Liu Shaohui Assignee: Liu Shaohui Priority: Minor Fix For: 2.0.0, 1.2.0, 1.1.2 Attachments: HBASE-14277-v001.diff, HBASE-14277-v002.diff After HBASE-13995, hostname will be converted to lower case in ServerName. It may cause the test: TestRegionServerHostname.testRegionServerHostname failed at host with a case sensitive name. Just fix it in test. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14298) Source assemblies incorrect after recent POM changes (0.98)
[
https://issues.apache.org/jira/browse/HBASE-14298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14708782#comment-14708782
]
Andrew Purtell commented on HBASE-14298:
Any idea what's going on here [~busbey]?
Source assemblies incorrect after recent POM changes (0.98)
---
Key: HBASE-14298
URL: https://issues.apache.org/jira/browse/HBASE-14298
Project: HBase
Issue Type: Bug
Affects Versions: 0.98.14
Reporter: Andrew Purtell
Priority: Blocker
Fix For: 0.98.14
After recent POM changes when building source assemblies:
{noformat}
$ mvn clean install -DskipTests assembly:single \
-Dassembly.file=hbase-assembly/src/main/assembly/src.xml -Prelease
{noformat}
several modules are now missing from the resulting tarball: hbase-assembly,
hbase-examples, hbase-it, hbase-resource-bundle, hbase-rest, hbase-shell,
hbase-testing-util, hbase-thrift
Here's what we should have:
{noformat}
bin
CHANGES.txt
conf
dev-support
hbase-annotations
hbase-assembly
hbase-checkstyle
hbase-client
hbase-common
hbase-examples
hbase-hadoop1-compat
hbase-hadoop2-compat
hbase-hadoop-compat
hbase-it
hbase-prefix-tree
hbase-protocol
hbase-resource-bundle
hbase-rest
hbase-server
hbase-shell
hbase-testing-util
hbase-thrift
LICENSE.txt
NOTICE.txt
pom.xml
README.txt
src
{noformat}
Here's what only shows up in the source tarball:
{noformat}
bin
CHANGES.txt
conf
dev-support
hbase-annotations
hbase-checkstyle
hbase-client
hbase-common
hbase-hadoop1-compat
hbase-hadoop2-compat
hbase-hadoop-compat
hbase-prefix-tree
hbase-protocol
hbase-resource-bundle
hbase-server
LICENSE.txt
NOTICE.txt
pom.xml
README.txt
src
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-14298) Source assemblies incorrect after recent POM changes (0.98)
Andrew Purtell created HBASE-14298:
--
Summary: Source assemblies incorrect after recent POM changes
(0.98)
Key: HBASE-14298
URL: https://issues.apache.org/jira/browse/HBASE-14298
Project: HBase
Issue Type: Bug
Affects Versions: 0.98.14
Reporter: Andrew Purtell
Priority: Blocker
Fix For: 0.98.14
After recent POM changes when building source assemblies:
{noformat}
$ mvn clean install -DskipTests assembly:single \
-Dassembly.file=hbase-assembly/src/main/assembly/src.xml -Prelease
{noformat}
several modules are now missing from the resulting tarball: hbase-assembly,
hbase-examples, hbase-it, hbase-resource-bundle, hbase-rest, hbase-shell,
hbase-testing-util, hbase-thrift
Here's what we should have:
{noformat}
bin
CHANGES.txt
conf
dev-support
hbase-annotations
hbase-assembly
hbase-checkstyle
hbase-client
hbase-common
hbase-examples
hbase-hadoop1-compat
hbase-hadoop2-compat
hbase-hadoop-compat
hbase-it
hbase-prefix-tree
hbase-protocol
hbase-resource-bundle
hbase-rest
hbase-server
hbase-shell
hbase-testing-util
hbase-thrift
LICENSE.txt
NOTICE.txt
pom.xml
README.txt
src
{noformat}
Here's what only shows up in the source tarball:
{noformat}
bin
CHANGES.txt
conf
dev-support
hbase-annotations
hbase-checkstyle
hbase-client
hbase-common
hbase-hadoop1-compat
hbase-hadoop2-compat
hbase-hadoop-compat
hbase-prefix-tree
hbase-protocol
hbase-resource-bundle
hbase-server
LICENSE.txt
NOTICE.txt
pom.xml
README.txt
src
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14293) TestStochasticBalancerJmxMetrics intermittently fails due to port conflict
[
https://issues.apache.org/jira/browse/HBASE-14293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14708706#comment-14708706
]
Lei Chen commented on HBASE-14293:
--
patch v3 looks good. +1
TestStochasticBalancerJmxMetrics intermittently fails due to port conflict
--
Key: HBASE-14293
URL: https://issues.apache.org/jira/browse/HBASE-14293
Project: HBase
Issue Type: Test
Reporter: Ted Yu
Assignee: Ted Yu
Priority: Minor
Fix For: 2.0.0
Attachments: 14293-v1.txt, 14293-v2.txt, 14293-v3.txt
From
https://builds.apache.org/job/HBase-TRUNK/6748/testReport/junit/org.apache.hadoop.hbase/TestStochasticBalancerJmxMetrics/testJmxMetrics_EnsembleMode/
:
{code}
2015-08-22 20:46:07,939 ERROR [M:0;asf900:59022]
coprocessor.CoprocessorHost(518): The coprocessor
org.apache.hadoop.hbase.JMXListener threw java.rmi.server.ExportException:
Port already in use: 61120; nested exception is:
java.net.BindException: Address already in use
java.rmi.server.ExportException: Port already in use: 61120; nested exception
is:
java.net.BindException: Address already in use
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:329)
at
sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:237)
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:411)
...
2015-08-22 20:49:41,755 DEBUG [main]
hbase.TestStochasticBalancerJmxMetrics(93): Encountered exception when
starting cluster. Trying port 61122
java.lang.IllegalStateException: A mini-cluster is already running
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:981)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:872)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:866)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:810)
at
org.apache.hadoop.hbase.TestStochasticBalancerJmxMetrics.setupBeforeClass(TestStochasticBalancerJmxMetrics.java:89)
{code}
When port conflict is detected, we try the next port.
However, HTU#miniClusterRunning is true by this moment, leading to the second
exception shown above.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-14296) ConnectionManager should validate the table existence before returning the table instance
Pankaj Kumar created HBASE-14296:
Summary: ConnectionManager should validate the table existence
before returning the table instance
Key: HBASE-14296
URL: https://issues.apache.org/jira/browse/HBASE-14296
Project: HBase
Issue Type: Bug
Components: Client
Affects Versions: 2.0.0, 1.2.0, 0.98.15
Reporter: Pankaj Kumar
Assignee: Pankaj Kumar
Priority: Minor
Table instance should be returned only when table exist.
{code}
public HTableInterface getTable(TableName tableName, ExecutorService pool)
throws IOException {
if (managed) {
throw new NeedUnmanagedConnectionException();
}
return new HTable(tableName, this, tableConfig, rpcCallerFactory,
rpcControllerFactory, pool);
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13480) ShortCircuitConnection doesn't short-circuit all calls as expected
[
https://issues.apache.org/jira/browse/HBASE-13480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jingcheng Du updated HBASE-13480:
-
Attachment: HBASE-13480-2.patch
Thanks guys for comments. A new patch is uploaded (V2).
# Use an anonymous class instead.
ShortCircuitConnection doesn't short-circuit all calls as expected
--
Key: HBASE-13480
URL: https://issues.apache.org/jira/browse/HBASE-13480
Project: HBase
Issue Type: Bug
Components: Client
Affects Versions: 1.0.0, 2.0.0, 1.1.0
Reporter: Josh Elser
Assignee: Jingcheng Du
Priority: Critical
Fix For: 2.0.0, 1.3.0, 1.2.1, 1.0.3, 1.1.3
Attachments: HBASE-13480-1.patch, HBASE-13480-2.patch,
HBASE-13480.patch
Noticed the following situation in debugging unexpected unit tests failures
in HBASE-13351.
{{ConnectionUtils#createShortCircuitHConnection(Connection, ServerName,
AdminService.BlockingInterface, ClientService.BlockingInterface)}} is
intended to avoid the extra RPC by calling the server's instantiation of the
protobuf rpc stub directly for the AdminService and ClientService.
The problem is that this is insufficient to actually avoid extra remote
RPCs as all other calls to the Connection are routed to a real Connection
instance. As such, any object created by the real Connection (such as an
HTable) will use the real Connection, not the SSC.
The end result is that
{{MasterRpcService#reportRegionStateTransition(RpcController,
ReportRegionStateTransitionRequest)}} will make additional remote RPCs over
what it thinks is an SSC through a {{Get}} on {{HTable}} which was
constructed using the SSC, but the {{Get}} itself will use the underlying
real Connection instead of the SSC. With insufficiently sized thread pools,
this has been observed to result in RPC deadlock in the HMaster where an RPC
attempts to make another RPC but there are no more threads available to
service the second RPC so the first RPC blocks indefinitely.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14277) TestRegionServerHostname.testRegionServerHostname may fail at host with a case sensitive name
[ https://issues.apache.org/jira/browse/HBASE-14277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14708747#comment-14708747 ] Liu Shaohui commented on HBASE-14277: - Push to master, branch-1.1 and branch-1.2. No need for 0.98 and branch 1.0 because they do not have this test. TestRegionServerHostname.testRegionServerHostname may fail at host with a case sensitive name - Key: HBASE-14277 URL: https://issues.apache.org/jira/browse/HBASE-14277 Project: HBase Issue Type: Test Components: test Affects Versions: 2.0.0 Reporter: Liu Shaohui Assignee: Liu Shaohui Priority: Minor Fix For: 2.0.0, 1.2.0, 1.1.2 Attachments: HBASE-14277-v001.diff, HBASE-14277-v002.diff After HBASE-13995, hostname will be converted to lower case in ServerName. It may cause the test: TestRegionServerHostname.testRegionServerHostname failed at host with a case sensitive name. Just fix it in test. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14277) TestRegionServerHostname.testRegionServerHostname may fail at host with a case sensitive name
[ https://issues.apache.org/jira/browse/HBASE-14277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liu Shaohui updated HBASE-14277: Resolution: Fixed Status: Resolved (was: Patch Available) TestRegionServerHostname.testRegionServerHostname may fail at host with a case sensitive name - Key: HBASE-14277 URL: https://issues.apache.org/jira/browse/HBASE-14277 Project: HBase Issue Type: Test Components: test Affects Versions: 2.0.0 Reporter: Liu Shaohui Assignee: Liu Shaohui Priority: Minor Fix For: 2.0.0, 1.2.0, 1.1.2 Attachments: HBASE-14277-v001.diff, HBASE-14277-v002.diff After HBASE-13995, hostname will be converted to lower case in ServerName. It may cause the test: TestRegionServerHostname.testRegionServerHostname failed at host with a case sensitive name. Just fix it in test. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14289) Backport HBASE-13965 'Stochastic Load Balancer JMX Metrics' to 0.98
[ https://issues.apache.org/jira/browse/HBASE-14289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-14289: --- Fix Version/s: (was: 0.98.14) 0.98.15 Backport HBASE-13965 'Stochastic Load Balancer JMX Metrics' to 0.98 --- Key: HBASE-14289 URL: https://issues.apache.org/jira/browse/HBASE-14289 Project: HBase Issue Type: Improvement Reporter: Ted Yu Assignee: Ted Yu Fix For: 0.98.15 Attachments: 14289-0.98-v2.txt The default HBase load balancer (the Stochastic load balancer) is cost function based. The cost function weights are tunable but no visibility into those cost function results is directly provided. This issue backports HBASE-13965 to 0.98 branch to provide visibility via JMX into each cost function of the stochastic load balancer, as well as the overall cost of the balancing plan. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14292) Call Me Maybe HBase links haved moved
[ https://issues.apache.org/jira/browse/HBASE-14292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-14292: --- Attachment: HBASE-14292.patch Call Me Maybe HBase links haved moved - Key: HBASE-14292 URL: https://issues.apache.org/jira/browse/HBASE-14292 Project: HBase Issue Type: Bug Components: documentation Reporter: Robert Yokota Assignee: Misty Stanley-Jones Priority: Minor Attachments: HBASE-14292.patch The links to the Yammer engineering blog have moved. Please use the following links in section 83.5. Network Consistency and Partition Tolerance http://old.eng.yammer.com/call-me-maybe-hbase/ http://old.eng.yammer.com/call-me-maybe-hbase-addendum/ Thanks -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HBASE-14298) Source assemblies incorrect after recent POM changes (0.98)
[
https://issues.apache.org/jira/browse/HBASE-14298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell reassigned HBASE-14298:
--
Assignee: Andrew Purtell
Source assemblies incorrect after recent POM changes (0.98)
---
Key: HBASE-14298
URL: https://issues.apache.org/jira/browse/HBASE-14298
Project: HBase
Issue Type: Bug
Affects Versions: 0.98.14
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Priority: Blocker
Fix For: 0.98.14
After recent POM changes when building source assemblies:
{noformat}
$ mvn clean install -DskipTests assembly:single \
-Dassembly.file=hbase-assembly/src/main/assembly/src.xml -Prelease
{noformat}
several modules are now missing from the resulting tarball: hbase-assembly,
hbase-examples, hbase-it, hbase-resource-bundle, hbase-rest, hbase-shell,
hbase-testing-util, hbase-thrift
Here's what we should have:
{noformat}
bin
CHANGES.txt
conf
dev-support
hbase-annotations
hbase-assembly
hbase-checkstyle
hbase-client
hbase-common
hbase-examples
hbase-hadoop1-compat
hbase-hadoop2-compat
hbase-hadoop-compat
hbase-it
hbase-prefix-tree
hbase-protocol
hbase-resource-bundle
hbase-rest
hbase-server
hbase-shell
hbase-testing-util
hbase-thrift
LICENSE.txt
NOTICE.txt
pom.xml
README.txt
src
{noformat}
Here's what only shows up in the source tarball:
{noformat}
bin
CHANGES.txt
conf
dev-support
hbase-annotations
hbase-checkstyle
hbase-client
hbase-common
hbase-hadoop1-compat
hbase-hadoop2-compat
hbase-hadoop-compat
hbase-prefix-tree
hbase-protocol
hbase-resource-bundle
hbase-server
LICENSE.txt
NOTICE.txt
pom.xml
README.txt
src
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-14298) Source assemblies incorrect after recent POM changes (0.98)
[
https://issues.apache.org/jira/browse/HBASE-14298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-14298:
---
Attachment: HBASE-14298-0.98.patch
Much better after this
Source assemblies incorrect after recent POM changes (0.98)
---
Key: HBASE-14298
URL: https://issues.apache.org/jira/browse/HBASE-14298
Project: HBase
Issue Type: Bug
Affects Versions: 0.98.14
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Priority: Blocker
Fix For: 0.98.14
Attachments: HBASE-14298-0.98.patch
After recent POM changes when building source assemblies:
{noformat}
$ mvn clean install -DskipTests assembly:single \
-Dassembly.file=hbase-assembly/src/main/assembly/src.xml -Prelease
{noformat}
several modules are now missing from the resulting tarball: hbase-assembly,
hbase-examples, hbase-it, hbase-resource-bundle, hbase-rest, hbase-shell,
hbase-testing-util, hbase-thrift
Here's what we should have:
{noformat}
bin
CHANGES.txt
conf
dev-support
hbase-annotations
hbase-assembly
hbase-checkstyle
hbase-client
hbase-common
hbase-examples
hbase-hadoop1-compat
hbase-hadoop2-compat
hbase-hadoop-compat
hbase-it
hbase-prefix-tree
hbase-protocol
hbase-resource-bundle
hbase-rest
hbase-server
hbase-shell
hbase-testing-util
hbase-thrift
LICENSE.txt
NOTICE.txt
pom.xml
README.txt
src
{noformat}
Here's what only shows up in the source tarball:
{noformat}
bin
CHANGES.txt
conf
dev-support
hbase-annotations
hbase-checkstyle
hbase-client
hbase-common
hbase-hadoop1-compat
hbase-hadoop2-compat
hbase-hadoop-compat
hbase-prefix-tree
hbase-protocol
hbase-resource-bundle
hbase-server
LICENSE.txt
NOTICE.txt
pom.xml
README.txt
src
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13995) ServerName is not fully case insensitive
[ https://issues.apache.org/jira/browse/HBASE-13995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liu Shaohui updated HBASE-13995: Fix Version/s: (was: 1.0.2) (was: 0.98.14) ServerName is not fully case insensitive Key: HBASE-13995 URL: https://issues.apache.org/jira/browse/HBASE-13995 Project: HBase Issue Type: Bug Components: Region Assignment Affects Versions: 2.0.0, 1.2.0, 0.98.12.1, 1.0.1.1, 1.1.0.1 Reporter: Matteo Bertozzi Assignee: Matteo Bertozzi Fix For: 2.0.0, 1.2.0, 1.1.2 Attachments: HBASE-13995-v0.patch, HBASE-13995-v0.patch we ended up with two ServerName with different cases, AAA and aaa. Trying to create a table, every once in a while, we ended up with the region lost and not assigned. BaseLoadBalancer.roundRobinAssignment() goes through each server and create a map with what to assign to them. We had to server on the list AAA and aaa which are the same machine, the problem is that the round robin now is assigning an empty list to one of the two. so depending on the order we ended up with a region not assigned. ServerName equals() does the case insensitive comparison but the hashCode() is done on a case sensitive server name, so the Map in ServerManager will never hit the item and compare it using equals, so we end up with two entries that are the same server. similar thing for ServerName.isSameHostnameAndPort() where we don't check for cases -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13995) ServerName is not fully case insensitive
[ https://issues.apache.org/jira/browse/HBASE-13995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liu Shaohui updated HBASE-13995: Fix Version/s: 0.98.14 1.0.2 ServerName is not fully case insensitive Key: HBASE-13995 URL: https://issues.apache.org/jira/browse/HBASE-13995 Project: HBase Issue Type: Bug Components: Region Assignment Affects Versions: 2.0.0, 1.2.0, 0.98.12.1, 1.0.1.1, 1.1.0.1 Reporter: Matteo Bertozzi Assignee: Matteo Bertozzi Fix For: 2.0.0, 0.98.14, 1.0.2, 1.2.0, 1.1.2 Attachments: HBASE-13995-v0.patch, HBASE-13995-v0.patch we ended up with two ServerName with different cases, AAA and aaa. Trying to create a table, every once in a while, we ended up with the region lost and not assigned. BaseLoadBalancer.roundRobinAssignment() goes through each server and create a map with what to assign to them. We had to server on the list AAA and aaa which are the same machine, the problem is that the round robin now is assigning an empty list to one of the two. so depending on the order we ended up with a region not assigned. ServerName equals() does the case insensitive comparison but the hashCode() is done on a case sensitive server name, so the Map in ServerManager will never hit the item and compare it using equals, so we end up with two entries that are the same server. similar thing for ServerName.isSameHostnameAndPort() where we don't check for cases -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-14297) Fix a long standing nit with 0.98 source assemblies
Andrew Purtell created HBASE-14297: -- Summary: Fix a long standing nit with 0.98 source assemblies Key: HBASE-14297 URL: https://issues.apache.org/jira/browse/HBASE-14297 Project: HBase Issue Type: Bug Reporter: Andrew Purtell Assignee: Andrew Purtell Priority: Trivial Fix For: 0.98.14 I have a custom RC script that manually fixes up a nit in source assembly builds. Make a proper fix for this. Trivial change, obvious bug. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14269) FuzzyRowFilter omits certain rows when multiple fuzzy key exist
[ https://issues.apache.org/jira/browse/HBASE-14269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14708712#comment-14708712 ] hongbin ma commented on HBASE-14269: Hi Vladimir, Sorry I didn't have internet access during the weekend. I'll work on a performance test on our real large dataset. For now I suggest merging this patch to at least guarantee correctness. Just a quick question, is there anything you want me to add/change in the latest patch(v2)? I'm a little bit confused by your comments. FuzzyRowFilter omits certain rows when multiple fuzzy key exist --- Key: HBASE-14269 URL: https://issues.apache.org/jira/browse/HBASE-14269 Project: HBase Issue Type: Bug Components: Filters Reporter: hongbin ma Assignee: hongbin ma Attachments: HBASE-14269-v1.patch, HBASE-14269-v2.patch, HBASE-14269.patch https://issues.apache.org/jira/browse/HBASE-13761 introduced a RowTracker in FuzzyRowFilter to avoid performing getNextForFuzzyRule() for each fuzzy key on each getNextCellHint() by maintaining a list of possible row matches for each fuzzy key. The implementation assumes that the prepared rows will be matched one by one, so it removes the first row in the list as soon as it is used. However, this approach may lead to omitting rows in some cases: Consider a case where we have two fuzzy keys: 1?1 2?2 and the data is like: 000 111 112 121 122 211 212 when the first row 000 fails to match, RowTracker will update possible row matches with cell 000 and fuzzy keys 1?1,2?2. This will populate RowTracker with 101 and 202. Then 101 is popped out of RowTracker, hint the scanner to go to row 101. The scanner will get 111 and find it is a match, and continued to find that 112 is not a match, getNextCellHint will be called again. Then comes the bug: Row 101 has been removed out of RowTracker, so RowTracker will jump to 202. As you see row 121 will be omitted, but it is actually a match for fuzzy key 1?1. I will illustrate the bug by adding a new test case in TestFuzzyRowFilterEndToEnd. Also I will provide the bug fix in my patch. The idea of the new solution is to maintain a priority queue for all the possible match rows for each fuzzy key, and whenever getNextCellHint is called, the elements in the queue that are smaller than the parameter currentCell will be updated(and re-insert into the queue). The head of queue will always be the Next cell hint. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14297) Fix a long standing nit with 0.98 source assemblies
[ https://issues.apache.org/jira/browse/HBASE-14297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-14297: --- Attachment: HBASE-14297-0.98.patch Tested this fix. Committing now so I can get the 0.98.14 RC1 out with it included. Should there be an issue we can revert the commit and pull the RC. Fix a long standing nit with 0.98 source assemblies --- Key: HBASE-14297 URL: https://issues.apache.org/jira/browse/HBASE-14297 Project: HBase Issue Type: Bug Reporter: Andrew Purtell Assignee: Andrew Purtell Priority: Trivial Fix For: 0.98.14 Attachments: HBASE-14297-0.98.patch I have a custom RC script that manually fixes up a nit in source assembly builds. Make a proper fix for this. Trivial change, obvious bug. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HBASE-14297) Fix a long standing nit with 0.98 source assemblies
[ https://issues.apache.org/jira/browse/HBASE-14297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell resolved HBASE-14297. Resolution: Fixed Fix a long standing nit with 0.98 source assemblies --- Key: HBASE-14297 URL: https://issues.apache.org/jira/browse/HBASE-14297 Project: HBase Issue Type: Bug Reporter: Andrew Purtell Assignee: Andrew Purtell Priority: Trivial Fix For: 0.98.14 Attachments: HBASE-14297-0.98.patch I have a custom RC script that manually fixes up a nit in source assembly builds. Make a proper fix for this. Trivial change, obvious bug. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14298) Source assemblies incorrect after recent POM changes (0.98)
[
https://issues.apache.org/jira/browse/HBASE-14298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14708786#comment-14708786
]
Andrew Purtell commented on HBASE-14298:
I'm going to bring back assembly descriptor changes we've had on branch-1 for a
while that do things differently. Let's remove some of this legacy stuff.
Source assemblies incorrect after recent POM changes (0.98)
---
Key: HBASE-14298
URL: https://issues.apache.org/jira/browse/HBASE-14298
Project: HBase
Issue Type: Bug
Affects Versions: 0.98.14
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Priority: Blocker
Fix For: 0.98.14
After recent POM changes when building source assemblies:
{noformat}
$ mvn clean install -DskipTests assembly:single \
-Dassembly.file=hbase-assembly/src/main/assembly/src.xml -Prelease
{noformat}
several modules are now missing from the resulting tarball: hbase-assembly,
hbase-examples, hbase-it, hbase-resource-bundle, hbase-rest, hbase-shell,
hbase-testing-util, hbase-thrift
Here's what we should have:
{noformat}
bin
CHANGES.txt
conf
dev-support
hbase-annotations
hbase-assembly
hbase-checkstyle
hbase-client
hbase-common
hbase-examples
hbase-hadoop1-compat
hbase-hadoop2-compat
hbase-hadoop-compat
hbase-it
hbase-prefix-tree
hbase-protocol
hbase-resource-bundle
hbase-rest
hbase-server
hbase-shell
hbase-testing-util
hbase-thrift
LICENSE.txt
NOTICE.txt
pom.xml
README.txt
src
{noformat}
Here's what only shows up in the source tarball:
{noformat}
bin
CHANGES.txt
conf
dev-support
hbase-annotations
hbase-checkstyle
hbase-client
hbase-common
hbase-hadoop1-compat
hbase-hadoop2-compat
hbase-hadoop-compat
hbase-prefix-tree
hbase-protocol
hbase-resource-bundle
hbase-server
LICENSE.txt
NOTICE.txt
pom.xml
README.txt
src
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (HBASE-14298) Source assemblies incorrect after recent POM changes (0.98)
[
https://issues.apache.org/jira/browse/HBASE-14298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14708786#comment-14708786
]
Andrew Purtell edited comment on HBASE-14298 at 8/24/15 5:32 AM:
-
I'm going to bring back assembly descriptor changes we've had on branch-1 for a
while that do things differently. Let's update some of this legacy stuff.
was (Author: apurtell):
I'm going to bring back assembly descriptor changes we've had on branch-1 for a
while that do things differently. Let's remove some of this legacy stuff.
Source assemblies incorrect after recent POM changes (0.98)
---
Key: HBASE-14298
URL: https://issues.apache.org/jira/browse/HBASE-14298
Project: HBase
Issue Type: Bug
Affects Versions: 0.98.14
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Priority: Blocker
Fix For: 0.98.14
Attachments: HBASE-14298-0.98.patch, HBASE-14298-0.98.patch
After recent POM changes when building source assemblies:
{noformat}
$ mvn clean install -DskipTests assembly:single \
-Dassembly.file=hbase-assembly/src/main/assembly/src.xml -Prelease
{noformat}
several modules are now missing from the resulting tarball: hbase-assembly,
hbase-examples, hbase-it, hbase-resource-bundle, hbase-rest, hbase-shell,
hbase-testing-util, hbase-thrift
Here's what we should have:
{noformat}
bin
CHANGES.txt
conf
dev-support
hbase-annotations
hbase-assembly
hbase-checkstyle
hbase-client
hbase-common
hbase-examples
hbase-hadoop1-compat
hbase-hadoop2-compat
hbase-hadoop-compat
hbase-it
hbase-prefix-tree
hbase-protocol
hbase-resource-bundle
hbase-rest
hbase-server
hbase-shell
hbase-testing-util
hbase-thrift
LICENSE.txt
NOTICE.txt
pom.xml
README.txt
src
{noformat}
Here's what only shows up in the source tarball:
{noformat}
bin
CHANGES.txt
conf
dev-support
hbase-annotations
hbase-checkstyle
hbase-client
hbase-common
hbase-hadoop1-compat
hbase-hadoop2-compat
hbase-hadoop-compat
hbase-prefix-tree
hbase-protocol
hbase-resource-bundle
hbase-server
LICENSE.txt
NOTICE.txt
pom.xml
README.txt
src
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-14298) Source assemblies incorrect after recent POM changes (0.98)
[
https://issues.apache.org/jira/browse/HBASE-14298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-14298:
---
Status: Patch Available (was: Open)
Source assemblies incorrect after recent POM changes (0.98)
---
Key: HBASE-14298
URL: https://issues.apache.org/jira/browse/HBASE-14298
Project: HBase
Issue Type: Bug
Affects Versions: 0.98.14
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Priority: Blocker
Fix For: 0.98.14
Attachments: HBASE-14298-0.98.patch, HBASE-14298-0.98.patch
After recent POM changes when building source assemblies:
{noformat}
$ mvn clean install -DskipTests assembly:single \
-Dassembly.file=hbase-assembly/src/main/assembly/src.xml -Prelease
{noformat}
several modules are now missing from the resulting tarball: hbase-assembly,
hbase-examples, hbase-it, hbase-resource-bundle, hbase-rest, hbase-shell,
hbase-testing-util, hbase-thrift
Here's what we should have:
{noformat}
bin
CHANGES.txt
conf
dev-support
hbase-annotations
hbase-assembly
hbase-checkstyle
hbase-client
hbase-common
hbase-examples
hbase-hadoop1-compat
hbase-hadoop2-compat
hbase-hadoop-compat
hbase-it
hbase-prefix-tree
hbase-protocol
hbase-resource-bundle
hbase-rest
hbase-server
hbase-shell
hbase-testing-util
hbase-thrift
LICENSE.txt
NOTICE.txt
pom.xml
README.txt
src
{noformat}
Here's what only shows up in the source tarball:
{noformat}
bin
CHANGES.txt
conf
dev-support
hbase-annotations
hbase-checkstyle
hbase-client
hbase-common
hbase-hadoop1-compat
hbase-hadoop2-compat
hbase-hadoop-compat
hbase-prefix-tree
hbase-protocol
hbase-resource-bundle
hbase-server
LICENSE.txt
NOTICE.txt
pom.xml
README.txt
src
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
