Anoop Sam John (JIRA | 13 Feb 05:31 2016
Picon

[jira] [Reopened] (HBASE-15079) TestMultiParallel.validateLoadedData AssertionError: null


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

Anoop Sam John reopened HBASE-15079:
------------------------------------

Reopening as I see test failures after commit of this Jira to 0.98
(No other fix branches have the test fail issue)
We need revert this commit?  
cc [~apurtell]

> TestMultiParallel.validateLoadedData AssertionError: null
> ---------------------------------------------------------
>
>                 Key: HBASE-15079
>                 URL: https://issues.apache.org/jira/browse/HBASE-15079
>             Project: HBase
>          Issue Type: Bug
>          Components: Client, flakey, test
>    Affects Versions: 2.0.0, 1.2.0, 1.3.0
>            Reporter: stack
>            Assignee: Heng Chen
>             Fix For: 2.0.0, 1.2.0, 1.3.0, 0.98.18
>
>         Attachments: HBASE-14915-branch-1.2.patch
>
>
> Saw this failure on internal rig:
> {code}
(Continue reading)

Duo Zhang (JIRA | 13 Feb 04:40 2016
Picon

[jira] [Created] (HBASE-15265) Implement an asynchronous FSHLog

Duo Zhang created HBASE-15265:
---------------------------------

             Summary: Implement an asynchronous FSHLog
                 Key: HBASE-15265
                 URL: https://issues.apache.org/jira/browse/HBASE-15265
             Project: HBase
          Issue Type: Sub-task
            Reporter: Duo Zhang
            Assignee: Duo Zhang

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

Duo Zhang (JIRA | 13 Feb 04:39 2016
Picon

[jira] [Created] (HBASE-15264) Implement a fan out HDFS OutputStream

Duo Zhang created HBASE-15264:
---------------------------------

             Summary: Implement a fan out HDFS OutputStream
                 Key: HBASE-15264
                 URL: https://issues.apache.org/jira/browse/HBASE-15264
             Project: HBase
          Issue Type: Sub-task
            Reporter: Duo Zhang
            Assignee: Duo Zhang

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

stack (JIRA | 13 Feb 03:35 2016
Picon

[jira] [Created] (HBASE-15263) TestIPv6NIOServerSocketChannel.testServerSocketFromLocalhostResolution can hang indefinetly

stack created HBASE-15263:
-----------------------------

             Summary: TestIPv6NIOServerSocketChannel.testServerSocketFromLocalhostResolution can hang indefinetly
                 Key: HBASE-15263
                 URL: https://issues.apache.org/jira/browse/HBASE-15263
             Project: HBase
          Issue Type: Sub-task
            Reporter: stack

Should have a timeout on this test at least. Stuck here:

{code}
"main" #1 prio=5 os_prio=0 tid=0x00007f3f9c008000 nid=0xca97 runnable [0x00007f3fa2e8c000]
   java.lang.Thread.State: RUNNABLE
        at org.apache.hadoop.hbase.HBaseTestingUtility$PortAllocator.randomFreePort(HBaseTestingUtility.java:3500)
        at org.apache.hadoop.hbase.HBaseTestingUtility.randomFreePort(HBaseTestingUtility.java:3450)
        at org.apache.hadoop.hbase.TestIPv6NIOServerSocketChannel.bindServerSocket(TestIPv6NIOServerSocketChannel.java:57)
        at org.apache.hadoop.hbase.TestIPv6NIOServerSocketChannel.testServerSocketFromLocalhostResolution(TestIPv6NIOServerSocketChannel.java:151)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:497)
        at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
        at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
        at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
        at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
        at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
        at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
        at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
(Continue reading)

stack (JIRA | 13 Feb 03:29 2016
Picon

[jira] [Created] (HBASE-15262) TestZooKeeperMainServer#testCommandLineWorks fails with CancelledKeyException

stack created HBASE-15262:
-----------------------------

             Summary: TestZooKeeperMainServer#testCommandLineWorks fails with CancelledKeyException
                 Key: HBASE-15262
                 URL: https://issues.apache.org/jira/browse/HBASE-15262
             Project: HBase
          Issue Type: Sub-task
            Reporter: stack

{code}
2016-02-11 11:34:50,418 ERROR [SyncThread:0] server.NIOServerCnxn(178): Unexpected Exception:
java.nio.channels.CancelledKeyException
        at sun.nio.ch.SelectionKeyImpl.ensureValid(SelectionKeyImpl.java:73)
        at sun.nio.ch.SelectionKeyImpl.interestOps(SelectionKeyImpl.java:77)
        at org.apache.zookeeper.server.NIOServerCnxn.sendBuffer(NIOServerCnxn.java:151)
        at org.apache.zookeeper.server.ZooKeeperServer.finishSessionInit(ZooKeeperServer.java:607)
        at org.apache.zookeeper.server.FinalRequestProcessor.processRequest(FinalRequestProcessor.java:181)
        at org.apache.zookeeper.server.SyncRequestProcessor.flush(SyncRequestProcessor.java:200)
        at org.apache.zookeeper.server.SyncRequestProcessor.run(SyncRequestProcessor.java:131)
[code}

The test is expecting zk to do a System.exit but an existing zk or previous test is getting us this
CancelledKeyException... 

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

(Continue reading)

huaxiang sun (JIRA | 13 Feb 00:00 2016
Picon

[jira] [Created] (HBASE-15261) Make Throwable t in DaughterOpener volatile

huaxiang sun created HBASE-15261:
------------------------------------

             Summary: Make Throwable t in DaughterOpener volatile
                 Key: HBASE-15261
                 URL: https://issues.apache.org/jira/browse/HBASE-15261
             Project: HBase
          Issue Type: Bug
          Components: regionserver
            Reporter: huaxiang sun
            Assignee: huaxiang sun
            Priority: Minor

In the region split process, daughter regions are opened in different threads, Throwable t is set in these
threads and it is checked in the calling thread. Need to make it volatile so the checking will not miss any
exceptions from opening daughter regions.

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

Andrew Purtell | 12 Feb 23:52 2016
Picon

Re: [VOTE] HBase 1.2.0 RC2

Also in the 0.98 history. 

> On Feb 12, 2016, at 12:04 PM, Nick Dimiduk <ndimiduk@...> wrote:
> 
>> On Fri, Feb 12, 2016 at 11:44 AM, Sean Busbey <busbey@...> wrote:
>> 
>> I *could* make 1.2.0 RC3 that just cherry picks HBASE-15252 onto RC2, but
>> that's going to make things a bit messy and possibly confusing for folks
>> who look for the 1.2.0 tag to be an ancestor of branch-1.2's HEAD.
> 
> We have no strict requirement that a previous release is a git ancestor of
> a later release. So long as the committed set of JIRAs matches, it's fine.
> There's a precedent of this already with earlier 1.x release candidates.
> 
> On Fri, Feb 12, 2016 at 1:16 PM, Andrew Purtell <andrew.purtell@...>
>> wrote:
>> 
>>> Same here. I have started with RC2 but can mostly carry findings to RC3
>>> given only one additional change.
>>> 
>>>> On Feb 12, 2016, at 8:56 AM, Elliott Clark <eclark@...> wrote:
>>>> 
>>>> -1 until the dataloss is fixed.
>>>> 
>>>> But assuming that's fixed I would be good for a short vote cycle for
>> the
>>>> next RC.
>>>> 
>>>>> On Fri, Feb 12, 2016 at 1:02 AM, 张铎 <palomino219 <at> gmail.com> wrote:
>>>>> 
(Continue reading)

Ankit Singhal (JIRA | 12 Feb 18:36 2016
Picon

[jira] [Created] (HBASE-15260) Should we check zero length value in checkAndMutate when null is passes as expected value?

Ankit Singhal created HBASE-15260:
-------------------------------------

             Summary: Should we check zero length value in checkAndMutate when null is passes as expected value?
                 Key: HBASE-15260
                 URL: https://issues.apache.org/jira/browse/HBASE-15260
             Project: HBase
          Issue Type: Bug
            Reporter: Ankit Singhal

Should we check zero length value in checkAndMutate when null is passes as expected value?
If yes, then I think we should update the documentation for checkAndPut with the same as sometimes column
are used for marker with no empty byte array.
{code}
If the passed value is null, the check
   * is for the lack of column (ie: non-existance)
boolean checkAndPut(byte[] row, byte[] family, byte[] qualifier,
    byte[] value, Put put) throws IOException;
{code}

otherwise , we should remove this check.
{code}
HRegion.class

 <at> Override
  public boolean checkAndMutate(byte [] row, byte [] family, byte [] qualifier,
      CompareOp compareOp, ByteArrayComparable comparator, Mutation w,
      boolean writeToWAL)
  throws IOException{
...
(Continue reading)

Andrew Purtell (JIRA | 12 Feb 18:24 2016
Picon

[jira] [Reopened] (HBASE-15219) Canary tool does not return non-zero exit code when one of regions is in stuck state


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

Andrew Purtell reopened HBASE-15219:
------------------------------------

This wasn't tested?

> Canary tool does not return non-zero exit code when one of regions is in stuck state 
> -------------------------------------------------------------------------------------
>
>                 Key: HBASE-15219
>                 URL: https://issues.apache.org/jira/browse/HBASE-15219
>             Project: HBase
>          Issue Type: Bug
>          Components: canary
>    Affects Versions: 0.98.16
>            Reporter: Vishal Khandelwal
>            Assignee: Ted Yu
>            Priority: Critical
>             Fix For: 2.0.0, 1.3.0, 1.2.1, 0.98.18
>
>         Attachments: HBASE-15219.v1.patch, HBASE-15219.v3.patch, HBASE-15219.v4.patch,
HBASE-15219.v5.patch, HBASE-15219.v7.patch
>
>
> {code}
> 2016-02-05 12:24:18,571 ERROR [pool-2-thread-7] tool.Canary - read from region
CAN_1,\x08\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00,1454667477865.00e77d07b8defe10704417fb99aa0418.
(Continue reading)

Nick Dimiduk | 12 Feb 18:16 2016
Picon
Gravatar

[DISCUSS] Retiring EOL branches

Devs,

How are we handling the retirement of old release lines? ASF policy
now requires all release tags be "permanent/archival", which is enforced by
pushing them to the 'rel' space. From my perspective, that means everything
else that's no longer under active development can be deleted. As a recent
example, Enis has declared 1.0.x to be concluded, so by that reasoning we
can drop branch-1.0 (assuming the release tags have hit rel, of course).

I haven't done a recent audit, but I think we have a bunch of old branches
from the SVN days that no longer see activity. They're not hurting
anything, but I think keeping the branch set limited to active release
lines will help make it clear where to focus energy, especially in light of
recent discussion on the time commitments of backporting issues. Anyone who
wants to post-facto make a release from a retired line will still have the
tag to work from.

Thoughts?
-n
Apache Jenkins Server | 12 Feb 16:02 2016
Picon

Successful: HBase Generate Website

Build status: Successful

If successful, the website and docs have been generated. If failed, skip to the bottom of this email.

Use the following commands to download the patch and apply it to a clean branch based on origin/asf-site. If
you prefer to keep the hbase-site repo around permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git

  cd hbase-site
  wget -O- https://builds.apache.org/job/hbase_generate_website/135/artifact/website.patch.zip
| funzip > 85e1d9a109341c5f4aabb0e82c96ab52e99a6d72.patch
  git fetch
  git checkout -b asf-site-85e1d9a109341c5f4aabb0e82c96ab52e99a6d72 origin/asf-site
  git am 85e1d9a109341c5f4aabb0e82c96ab52e99a6d72.patch

At this point, you can preview the changes by opening index.html or any of the other HTML pages in your local
asf-site-85e1d9a109341c5f4aabb0e82c96ab52e99a6d72 branch, and you can review the differences by running:

  git diff origin/asf-site

There are lots of spurious changes, such as timestamps and CSS styles in tables. To see a list of files that
have been added, deleted, renamed, changed type, or are otherwise interesting, use the following command:

  git diff --name-status --diff-filter=ADCRTXUB origin/asf-site

To see only files that had 100 or more lines changed:

  git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'

(Continue reading)


Gmane