[jira] [Created] (HBASE-10173) Need HFile version check in VisibilityController.

2013-12-15 Thread Anoop Sam John (JIRA)
Anoop Sam John created HBASE-10173:
--

 Summary: Need HFile version check in VisibilityController.
 Key: HBASE-10173
 URL: https://issues.apache.org/jira/browse/HBASE-10173
 Project: HBase
  Issue Type: Improvement
  Components: security
Affects Versions: 0.98.0
Reporter: Anoop Sam John
Assignee: Anoop Sam John
 Fix For: 0.98.0, 0.99.0


Cell level visibility labels are stored as cell tags. So HFile V3 is the 
minimum version which can support this feature. Better to have a version check 
in VisibilityController. Some one using this CP but with any HFile version as 
V2, we can better throw error.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)


[jira] [Created] (HBASE-10172) hbase upgrade -check error

2013-12-15 Thread wang xiyi (JIRA)
wang xiyi created HBASE-10172:
-

 Summary: hbase upgrade -check error
 Key: HBASE-10172
 URL: https://issues.apache.org/jira/browse/HBASE-10172
 Project: HBase
  Issue Type: Bug
Reporter: wang xiyi






--
This message was sent by Atlassian JIRA
(v6.1.4#6159)


[jira] [Created] (HBASE-10171) Coprocessor improvement

2013-12-15 Thread Jingcheng Du (JIRA)
Jingcheng Du created HBASE-10171:


 Summary: Coprocessor improvement
 Key: HBASE-10171
 URL: https://issues.apache.org/jira/browse/HBASE-10171
 Project: HBase
  Issue Type: New Feature
  Components: Coprocessors
Affects Versions: 0.99.0
Reporter: Jingcheng Du
Assignee: Jingcheng Du


This umbrella JIRA includes some improvements of the coprocessor.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)


[jira] [Created] (HBASE-10170) Coprocessor task monitor

2013-12-15 Thread Jingcheng Du (JIRA)
Jingcheng Du created HBASE-10170:


 Summary: Coprocessor task monitor
 Key: HBASE-10170
 URL: https://issues.apache.org/jira/browse/HBASE-10170
 Project: HBase
  Issue Type: New Feature
  Components: Coprocessors
Reporter: Jingcheng Du


The coprocessor tasks are managed by the TaskMonitor in the server side. 
Usually these tasks run in a random long time, it’s hard to know how many tasks 
and how about the task status in the HRegionServer in the client side. 
To add the client API for the coprocessor task monitor could improve that. 
Users could find the coprocessor task status by categories(coprocessor, client, 
user name, etc.), this is helpful to improve the lives of the operations guys 
who have to run HBase in production by giving them an API that can integrate 
HBase server and coprocessor task monitoring with Nagios etc.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)


[jira] [Created] (HBASE-10169) Batch coprocessor

2013-12-15 Thread Jingcheng Du (JIRA)
Jingcheng Du created HBASE-10169:


 Summary: Batch coprocessor
 Key: HBASE-10169
 URL: https://issues.apache.org/jira/browse/HBASE-10169
 Project: HBase
  Issue Type: New Feature
  Components: Coprocessors
Reporter: Jingcheng Du


This is designed to improve the coprocessor invocation in the client side. 
Currently the coprocessor invocation is to send a call to each region. If 
there’s one region server, and 100 regions are located in this server, each 
coprocessor invocation will send 100 calls, each call uses a single thread in 
the client side. The threads will run out soon when the coprocessor invocations 
are heavy. 
In this design, all the calls to the same region server will be grouped into 
one in a single coprocessor invocation. This call will be spread into each 
region in the server side, and the results will be merged ahead in the server 
side before being returned to the client.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)


Re: ANN: The third hbase-0.96.1 release candidate is available for download

2013-12-15 Thread Jonathan Hsieh
+1

Ran on a 5-node hadoop 2.1 variant.
Ran the incrementer test that shotdown rc1.  It passes.
Looked at included docs, looks good.



On Fri, Dec 13, 2013 at 10:37 AM, Elliott Clark  wrote:

> +1
>
> Downloaded
> Checked the signature of all the tar.gz's
> Installed on a cluster (Hadoop 2.2 and Java 7u25)
> Ran PE
> Ran YCSB
> * The performance of this release is much better than 0.96.0.
>  Ran IT tests for ~16 hours
> * No data loss
> * IntegrationTestBigLinkedList
> * IntegrationTestIngest
> * IntegrationTestLoadAndVeirfy
> * IntegrationTestBulkLoad
> * IntegrationTestImportTsv
> * Everything was run with calm and slow deterministic monkeys
> * Everything completed successfully
> Tested the Canary. It performed its job well
> Tested HBase with lz4 compression
>
>
>
> On Tue, Dec 10, 2013 at 10:55 AM, Stack  wrote:
>
> > The third hbase-0.96.1 release candidate is available for download:
> >
> >   http://people.apache.org/~stack/hbase-0.96.1RC2/
> >
> > The maven artifacts are available here:
> >
> >   https://repository.apache.org/content/repositories/orgapachehbase-037/
> >
> > 152 issues [1] have been fixed since 0.96.0, mostly performance
> improvement
> > and bug fixes.
> >
> > Shall we release this as hbase-0.96.1?  Please vote by Monday, December
> > 16th.
> >
> > Thanks,
> > Your HBase Team
> >
> > 1. http://goo.gl/ZgYBW2
> >
>



-- 
// Jonathan Hsieh (shay)
// Software Engineer, Cloudera
// j...@cloudera.com


Re: ANN: The third hbase-0.96.1 release candidate is available for download

2013-12-15 Thread Andrew Purtell
+1

Checked signatures
Unpacked tarball - looks ok
Ran unit test suite - passed
Ran LoadTestTool with write+read+update up to 1M keys in minicluster
configuration - looks good

I don't think HBASE-10145 is a blocker.


On Tue, Dec 10, 2013 at 10:55 AM, Stack  wrote:

> The third hbase-0.96.1 release candidate is available for download:
>
>   http://people.apache.org/~stack/hbase-0.96.1RC2/
>
> The maven artifacts are available here:
>
>   https://repository.apache.org/content/repositories/orgapachehbase-037/
>
> 152 issues [1] have been fixed since 0.96.0, mostly performance improvement
> and bug fixes.
>
> Shall we release this as hbase-0.96.1?  Please vote by Monday, December
> 16th.
>
> Thanks,
> Your HBase Team
>
> 1. http://goo.gl/ZgYBW2
>



-- 
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)


[jira] [Created] (HBASE-10168) JNI implementation of HBase C APIs for 0.94.x releases

2013-12-15 Thread Aditya Kishore (JIRA)
Aditya Kishore created HBASE-10168:
--

 Summary: JNI implementation of HBase C APIs for 0.94.x releases
 Key: HBASE-10168
 URL: https://issues.apache.org/jira/browse/HBASE-10168
 Project: HBase
  Issue Type: Task
  Components: Client
Affects Versions: 0.94.14
Reporter: Aditya Kishore
Assignee: Aditya Kishore






--
This message was sent by Atlassian JIRA
(v6.1.4#6159)


[jira] [Created] (HBASE-10167) {pre|post}BatchMutate hooks should be used in row mutations.

2013-12-15 Thread rajeshbabu (JIRA)
rajeshbabu created HBASE-10167:
--

 Summary: {pre|post}BatchMutate hooks should be used in row 
mutations.
 Key: HBASE-10167
 URL: https://issues.apache.org/jira/browse/HBASE-10167
 Project: HBase
  Issue Type: Bug
  Components: Coprocessors
Reporter: rajeshbabu
Assignee: rajeshbabu


In multirow mutations preBatchMutate and postBatchMutate hooks are not getting 
used. These may be required in some cases. Mainly its useful in secondary index 
to prepare index table mutations based on row mutations. 



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)


[jira] [Resolved] (HBASE-10164) Allow heapsize of different units to be passed as HBASE_HEAPSIZE

2013-12-15 Thread Ted Yu (JIRA)

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

Ted Yu resolved HBASE-10164.


Resolution: Fixed

> Allow heapsize of different units to be passed as HBASE_HEAPSIZE
> 
>
> Key: HBASE-10164
> URL: https://issues.apache.org/jira/browse/HBASE-10164
> Project: HBase
>  Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: Ted Yu
> Fix For: 0.98.0, 0.99.0
>
> Attachments: 10164-v1.txt, 10164-v2.txt
>
>
> Currently HBASE_HEAPSIZE doesn't expect units.
> {code}
> $ HBASE_HEAPSIZE=5G /usr/lib/hbase/bin/hbase shell
> Invalid maximum heap size: -Xmx5Gm
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> {code}
> It would be more user friendly if different units of heapsize can be passed 
> through HBASE_HEAPSIZE
> If unit ('m' or 'G') is specified, 'm' doesn't need to be appended.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)