[jira] [Created] (HBASE-11369) The proceduce of interrupting current split task should be updated after HBASE-9736.

2014-06-17 Thread Liu Shaohui (JIRA)
Liu Shaohui created HBASE-11369:
---

 Summary: The proceduce of interrupting current split task should 
be updated after HBASE-9736.
 Key: HBASE-11369
 URL: https://issues.apache.org/jira/browse/HBASE-11369
 Project: HBase
  Issue Type: Bug
  Components: wal
Reporter: Liu Shaohui
Priority: Minor


Before HBASE-9736, SplitLogWorker only split one hlog at a time. When the data 
of znode for this task is changed (task is timeouted and resigned by 
splitLogManager), zookeeper will notify the SplitLogWorker. If this log task is 
owned by other regionserver, the SplitLogWorker will interrupt current task and 
try to get another task.

HBASE-9736 allow multi log splitters per RS so there will be multi current 
tasks running in the thread pool in SplitLogWorker.
So the proceduce of Interrupting current split task need be updated.

[~jeffreyz]  [~stack]






--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Resolved] (HBASE-11365) NavigableMap returned by a 'reversed' scanner has qualifiers ordered in the natural order and not the reversed one

2014-06-17 Thread Mathias Herberts (JIRA)

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

Mathias Herberts resolved HBASE-11365.
--

Resolution: Not a Problem

 NavigableMap returned by a 'reversed' scanner has qualifiers ordered in the 
 natural order and not the reversed one
 --

 Key: HBASE-11365
 URL: https://issues.apache.org/jira/browse/HBASE-11365
 Project: HBase
  Issue Type: Bug
  Components: Client
Reporter: Mathias Herberts

 Maybe this is a misconception on my side, but I assumed that the 'cells' 
 returned by a reverse scanner (HBASE-4811) would be in reverse order, not 
 just the rows.
 Was I wrong in my assumption?



--
This message was sent by Atlassian JIRA
(v6.2#6252)


HBase 0.98.x dependency problems

2014-06-17 Thread Konstantin Boudnik
Guys,

I have noticed an interesting problem with HBase 0.98 line. I have ended up with
a crappy Hadoop 2.2.0 artifacts in my local M2 cache - don't ask me how that
happen ;( - which causes compilation problems in HBase. And that brought this
whole issue into the light. Here's the essence of it:

while running for hbase-server module
  % mvn dependency:tree  -Dhadoop.version=2.3.0
I am getting a reference to hadoop 2.2.0

[INFO] +- org.apache.hadoop:hadoop-common:jar:2.2.0:compile
..
[INFO] +- org.apache.hadoop:hadoop-auth:jar:2.2.0:compile
[INFO] +- org.apache.hadoop:hadoop-client:jar:2.2.0:compile

This only happens for 0.98. On master the reference goes to 2.4.0
The problem here is that -Dhadoop.version is being seemingly ignored, which
might lead to binaries with dependencies inconsistent with what it was built
against. I am not sure if this had came up before, but certainly would
appreciate the community's input, if any.

Thanks a lot!
-- 
Take care,
  Cos



Re: HBase 0.98.x dependency problems

2014-06-17 Thread Ted Yu
Have you tried the following command ?

mvn dependency:tree -Dhadoop-two.version=2.3.0

The output of the above has 2.3.0 as the dependency.

Cheers


On Tue, Jun 17, 2014 at 11:40 AM, Konstantin Boudnik c...@apache.org wrote:

 Guys,

 I have noticed an interesting problem with HBase 0.98 line. I have ended
 up with
 a crappy Hadoop 2.2.0 artifacts in my local M2 cache - don't ask me how
 that
 happen ;( - which causes compilation problems in HBase. And that brought
 this
 whole issue into the light. Here's the essence of it:

 while running for hbase-server module
   % mvn dependency:tree  -Dhadoop.version=2.3.0
 I am getting a reference to hadoop 2.2.0

 [INFO] +- org.apache.hadoop:hadoop-common:jar:2.2.0:compile
 ..
 [INFO] +- org.apache.hadoop:hadoop-auth:jar:2.2.0:compile
 [INFO] +- org.apache.hadoop:hadoop-client:jar:2.2.0:compile

 This only happens for 0.98. On master the reference goes to 2.4.0
 The problem here is that -Dhadoop.version is being seemingly ignored, which
 might lead to binaries with dependencies inconsistent with what it was
 built
 against. I am not sure if this had came up before, but certainly would
 appreciate the community's input, if any.

 Thanks a lot!
 --
 Take care,
   Cos




[jira] [Created] (HBASE-11370) SSH doesn't need to scan meta if not using ZK for assignment

2014-06-17 Thread Jimmy Xiang (JIRA)
Jimmy Xiang created HBASE-11370:
---

 Summary: SSH doesn't need to scan meta if not using ZK for 
assignment
 Key: HBASE-11370
 URL: https://issues.apache.org/jira/browse/HBASE-11370
 Project: HBase
  Issue Type: Improvement
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
Priority: Minor


If we don't use ZK for assignment, the meta content should be the same as that 
in memory. So we should be able to avoid a meta scan.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Created] (HBASE-11371) Typo in Thrift2 docs

2014-06-17 Thread Cesar Delgado (JIRA)
Cesar Delgado created HBASE-11371:
-

 Summary: Typo in Thrift2 docs
 Key: HBASE-11371
 URL: https://issues.apache.org/jira/browse/HBASE-11371
 Project: HBase
  Issue Type: Bug
  Components: documentation
Affects Versions: 0.98.0
Reporter: Cesar Delgado


There seems to be a typo in the Thrift2 documentation with the example on how 
to start it.  The example shows this:

{{./bin/hbase-daemon.sh stop thrift}}

When it should be this:

{{./bin/hbase-daemon.sh stop thrift2}}



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Created] (HBASE-11372) Remove SlabCache

2014-06-17 Thread Nick Dimiduk (JIRA)
Nick Dimiduk created HBASE-11372:


 Summary: Remove SlabCache
 Key: HBASE-11372
 URL: https://issues.apache.org/jira/browse/HBASE-11372
 Project: HBase
  Issue Type: Task
  Components: regionserver
Affects Versions: 0.99.0
Reporter: Nick Dimiduk
 Fix For: 0.99.0


Per title.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Resolved] (HBASE-11366) Backport HBASE-4089 (block cache contents report UI) to 0.98

2014-06-17 Thread stack (JIRA)

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

stack resolved HBASE-11366.
---

Resolution: Fixed
  Assignee: stack

Pushed to 0.98 branch.

 Backport HBASE-4089 (block cache contents report UI) to 0.98
 

 Key: HBASE-11366
 URL: https://issues.apache.org/jira/browse/HBASE-11366
 Project: HBase
  Issue Type: Task
Reporter: Andrew Purtell
Assignee: stack
Priority: Minor
 Fix For: 0.98.4

 Attachments: 11366.txt


 Backport HBASE-4089 + HBASE-11329.
 Block caching is an active area of investigation and development. This is a 
 nice facility that provides convenient introspection capabilities in UI.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


Re: HBase 0.98.x dependency problems

2014-06-17 Thread Konstantin Boudnik
Thank you very much Ted - that helped beautifully! I think the build system
becomes a product on its own :)

Regards,
  Cos

On Tue, Jun 17, 2014 at 12:40PM, Ted Yu wrote:
 Have you tried the following command ?
 
 mvn dependency:tree -Dhadoop-two.version=2.3.0
 
 The output of the above has 2.3.0 as the dependency.
 
 Cheers
 
 
 On Tue, Jun 17, 2014 at 11:40 AM, Konstantin Boudnik c...@apache.org wrote:
 
  Guys,
 
  I have noticed an interesting problem with HBase 0.98 line. I have ended
  up with
  a crappy Hadoop 2.2.0 artifacts in my local M2 cache - don't ask me how
  that
  happen ;( - which causes compilation problems in HBase. And that brought
  this
  whole issue into the light. Here's the essence of it:
 
  while running for hbase-server module
% mvn dependency:tree  -Dhadoop.version=2.3.0
  I am getting a reference to hadoop 2.2.0
 
  [INFO] +- org.apache.hadoop:hadoop-common:jar:2.2.0:compile
  ..
  [INFO] +- org.apache.hadoop:hadoop-auth:jar:2.2.0:compile
  [INFO] +- org.apache.hadoop:hadoop-client:jar:2.2.0:compile
 
  This only happens for 0.98. On master the reference goes to 2.4.0
  The problem here is that -Dhadoop.version is being seemingly ignored, which
  might lead to binaries with dependencies inconsistent with what it was
  built
  against. I am not sure if this had came up before, but certainly would
  appreciate the community's input, if any.
 
  Thanks a lot!
  --
  Take care,
Cos
 
 


[jira] [Resolved] (HBASE-9131) Add admin-level documention about configuration and usage of the Bucket Cache

2014-06-17 Thread stack (JIRA)

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

stack resolved HBASE-9131.
--

Resolution: Done

Resolving as done by changes to doc by Misty recently and by HBASE-11364

 Add admin-level documention about configuration and usage of the Bucket Cache
 -

 Key: HBASE-9131
 URL: https://issues.apache.org/jira/browse/HBASE-9131
 Project: HBase
  Issue Type: Bug
Reporter: Jonathan Hsieh
 Attachments: hbase-9131.patch


 HBASE-7404 added the bucket cache but its configuration settings are 
 currently undocumented.  Without documentation developers would be the only 
 ones aware of the feature.
 Specifically documentation about slide 23 from 
 http://www.slideshare.net/cloudera/operations-session-4 would be great to add!



--
This message was sent by Atlassian JIRA
(v6.2#6252)