RE: com/google/protobuf/Message not found Exception
Dell Customer Communication Thanks Ted and Zhang for the replies. Yes, I got it work by adding a bundle in feature.xml of Karaf. Thanks, YuLing -Original Message- From: 张铎 [mailto:palomino...@gmail.com] Sent: Thursday, February 05, 2015 5:56 PM To: dev@hbase.apache.org Subject: Re: com/google/protobuf/Message not found Exception I'm not familiar with Karaf so I do not know what is a "feature" in Karaf. But hbase-client depends on many other jars, so usually you need to deploy them all, not only the hbase-client.jar and hadoop.jar. And for java programs, some people use maven-shade-plugin to pack a big jar with all dependencies in it and deploy it. Hope this could help. 2015-02-06 8:38 GMT+08:00 : > Dell Customer Communication > > Hi All, > > I'm getting NoClassFound exception for /com/google/protobuf/Message > while getting connection to HTable in HBase. I am running HBase server > single node on a VM with HBaseClient running on OSGI Karaf. I'm using > the HBase 0.94.15 and Hadoop 1.0.4. I wrapped these two jars as > feature and deployed on Karaf. > > Any idea why this exception is thrown on Karaf? Which jar HBase > 0.94.15 is using for this class? Do I need to deploy anything extra on Karaf? > > Thanks, > > YuLing > > Caused by: java.lang.ClassNotFoundException: > com.google.protobuf.Message > > at > org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(Bundle > Loader > .java:501) > > at > org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.j > ava:42 > 1) > > at > org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.j > ava:41 > 2) > > at > org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(Def > aultCl > assLoader.java:107) > > at java.lang.ClassLoader.loadClass(ClassLoader.java:358) > > ... 64 more > > >
Re: com/google/protobuf/Message not found Exception
I'm not familiar with Karaf so I do not know what is a "feature" in Karaf. But hbase-client depends on many other jars, so usually you need to deploy them all, not only the hbase-client.jar and hadoop.jar. And for java programs, some people use maven-shade-plugin to pack a big jar with all dependencies in it and deploy it. Hope this could help. 2015-02-06 8:38 GMT+08:00 : > Dell Customer Communication > > Hi All, > > I'm getting NoClassFound exception for /com/google/protobuf/Message > while getting connection to HTable in HBase. I am running HBase server > single node on a VM with HBaseClient running on OSGI Karaf. I'm using the > HBase 0.94.15 and Hadoop 1.0.4. I wrapped these two jars as feature and > deployed on Karaf. > > Any idea why this exception is thrown on Karaf? Which jar HBase 0.94.15 is > using for this class? Do I need to deploy anything extra on Karaf? > > Thanks, > > YuLing > > Caused by: java.lang.ClassNotFoundException: com.google.protobuf.Message > > at > org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader > .java:501) > > at > org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:42 > 1) > > at > org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:41 > 2) > > at > org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultCl > assLoader.java:107) > > at java.lang.ClassLoader.loadClass(ClassLoader.java:358) > > ... 64 more > > >
Re: com/google/protobuf/Message not found Exception
You can search in hbase source code: import com.google.protobuf.Message; ./src/main/java/org/apache/hadoop/hbase/io/HbaseObjectWritable.java com.google.protobuf.Message.class, ./src/main/java/org/apache/hadoop/hbase/mapreduce/TableMapReduceUtil.java >From dependency tree: [INFO] org.apache.hbase:hbase:jar:0.94.26 ... [INFO] +- com.google.protobuf:protobuf-java:jar:2.4.0a:compile Please include the protobuf jar as feature. Cheers On Thu, Feb 5, 2015 at 4:38 PM, wrote: > Dell Customer Communication > > Hi All, > > I'm getting NoClassFound exception for /com/google/protobuf/Message > while getting connection to HTable in HBase. I am running HBase server > single node on a VM with HBaseClient running on OSGI Karaf. I'm using the > HBase 0.94.15 and Hadoop 1.0.4. I wrapped these two jars as feature and > deployed on Karaf. > > Any idea why this exception is thrown on Karaf? Which jar HBase 0.94.15 is > using for this class? Do I need to deploy anything extra on Karaf? > > Thanks, > > YuLing > > Caused by: java.lang.ClassNotFoundException: com.google.protobuf.Message > > at > org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader > .java:501) > > at > org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:42 > 1) > > at > org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:41 > 2) > > at > org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultCl > assLoader.java:107) > > at java.lang.ClassLoader.loadClass(ClassLoader.java:358) > > ... 64 more > > >
com/google/protobuf/Message not found Exception
Dell Customer Communication Hi All, I'm getting NoClassFound exception for /com/google/protobuf/Message while getting connection to HTable in HBase. I am running HBase server single node on a VM with HBaseClient running on OSGI Karaf. I'm using the HBase 0.94.15 and Hadoop 1.0.4. I wrapped these two jars as feature and deployed on Karaf. Any idea why this exception is thrown on Karaf? Which jar HBase 0.94.15 is using for this class? Do I need to deploy anything extra on Karaf? Thanks, YuLing Caused by: java.lang.ClassNotFoundException: com.google.protobuf.Message at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader .java:501) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:42 1) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:41 2) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultCl assLoader.java:107) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) ... 64 more
[jira] [Reopened] (HBASE-12958) SSH doing hbase:meta get but hbase:meta not assigned
[
https://issues.apache.org/jira/browse/HBASE-12958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack reopened HBASE-12958:
---
Reverted branch-1*. Reopening till get them in.
> SSH doing hbase:meta get but hbase:meta not assigned
>
>
> Key: HBASE-12958
> URL: https://issues.apache.org/jira/browse/HBASE-12958
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0, 1.0.1, 1.1.0, 0.98.11
>
> Attachments: 12958.branch-1.v2.txt, 12958.txt, 12958v2.txt,
> 12958v2.txt, HBASE-12958-0.98-addendum.patch
>
>
> All master threads are blocked waiting on this call to return:
> {code}
> "MASTER_SERVER_OPERATIONS-c2020:16020-2" #189 prio=5 os_prio=0
> tid=0x7f4b0408b000 nid=0x7821 in Object.wait() [0x7f4ada24d000]
>java.lang.Thread.State: TIMED_WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at
> org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithRetries(RpcRetryingCaller.java:168)
> - locked <0x00041c374f50> (a
> java.util.concurrent.atomic.AtomicBoolean)
> at org.apache.hadoop.hbase.client.HTable.get(HTable.java:881)
> at
> org.apache.hadoop.hbase.MetaTableAccessor.get(MetaTableAccessor.java:208)
> at
> org.apache.hadoop.hbase.MetaTableAccessor.getRegionLocation(MetaTableAccessor.java:250)
> at
> org.apache.hadoop.hbase.MetaTableAccessor.getRegion(MetaTableAccessor.java:225)
> at
> org.apache.hadoop.hbase.master.RegionStates.serverOffline(RegionStates.java:634)
> - locked <0x00041c1f0d80> (a
> org.apache.hadoop.hbase.master.RegionStates)
> at
> org.apache.hadoop.hbase.master.AssignmentManager.processServerShutdown(AssignmentManager.java:3298)
> at
> org.apache.hadoop.hbase.master.handler.ServerShutdownHandler.process(ServerShutdownHandler.java:226)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:128)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Master is stuck trying to find hbase:meta on the server that just crashed and
> that we just recovered:
> Mon Feb 02 23:00:02 PST 2015, null, java.net.SocketTimeoutException:
> callTimeout=6, callDuration=68181: row '' on table 'hbase:meta' at
> region=hbase:meta,,1.1588230740,
> hostname=c2022.halxg.cloudera.com,16020,1422944918568, seqNum=0
> Will add more detail in a sec.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: [VOTE] Fourth release candidate for HBase 1.0.0 (RC3) is available. Please vote by Feb 11 2015
Thanks for the tests so far. Unfortunately, I think HBASE-12956 is an important regression to fix. I'll let RC3 sink as well, and will spin up a new one when that is fixed. Please feel free to continue the testing on this RC though for other tests. The changes in the next RC should not be too much. Enis On Thu, Feb 5, 2015 at 12:47 PM, Ted Yu wrote: > Did some more testing: > > Compiled Hive trunk against published maven artifacts > Used shell to exercise various commands, including update_all_config > command (verified by reloading regionserver:60030/conf) > > All looked good. > > On Tue, Feb 3, 2015 at 10:32 AM, Ted Yu wrote: > > > +1 based on the following: > > > > Checked signature > > Ran test suite > > Loaded tarball on a 5-node cluster > > Ran LoadTestTool which passed > > > > Will continue testing. > > > > On Mon, Feb 2, 2015 at 5:11 PM, Enis Söztutar wrote: > > > >> To get the ball rolling, here are the tests that I have done so far. No > >> official +1 yet, since I will spend some more time on this. > >> > >> - checked checksums, sigs > >> - checked the bin and src artifacts > >> - checked layouts > >> - checked java files in src tarball, and jar files in bin tarball > >> - checked the book and the site (they are new style) > >> - checked javadocs for both devapi and userapi > >> - checked reported version, build time, revision > >> - run some smoke tests using shell > >> - started local mode > >> - run LTT local mode > >> - checked the webUI in local mode > >> - checked JMX dump and debug dump > >> > >> I had run most of the ITs on the other RC's, but I'll repeat them for > this > >> and report here when done. > >> > >> Happy testing, > >> Enis > >> > >> On Sun, Feb 1, 2015 at 6:38 PM, Enis Söztutar wrote: > >> > >> > It gives me great pleasure to announce that the fourth release > candidate > >> > for the release > >> > 1.0.0 (HBase-1.0.0RC3), is available for download at > >> > https://dist.apache.org/repos/dist/dev/hbase/hbase-1.0.0RC3/ > >> > > >> > Maven artifacts are also available in the temporary repository > >> > > https://repository.apache.org/content/repositories/orgapachehbase-1061 > >> > > >> > Signed with my code signing key E964B5FF. Can be found here: > >> > https://people.apache.org/keys/committer/enis.asc > >> > > >> > Signed tag in the repository can be found here: > >> > > >> > > >> > https://git-wip-us.apache.org/repos/asf?p=hbase.git;a=tag;h=46d9c29d83b535781e8fa8a044c12ee990a002c3 > >> > > >> > HBase 1.0.0 is the next stable release, and the start of "semantic > >> > versioned" > >> > releases (See [1]). > >> > > >> > The theme of 1.0.0 release is to become a stable base for future 1.x > >> series > >> > of releases. We aim to achieve at least the same level of stability of > >> 0.98 > >> > releases. > >> > > >> > 1.0.0 release contains 167 fixes on top of 0.99.2 release. Together > with > >> > the > >> > previous 0.99.x releases, major changes in 1.0.0 are listed (but not > >> > limited to) > >> > below. Note that all previous 0.99.x releases are developer preview > >> > releases, and will > >> > NOT be supported in any form. > >> > > >> > API Cleanup and changes > >> > 1.0.0 introduces new APIs, and deprecates some of commonly-used > >> > client side APIs (HTableInterface, HTable and HBaseAdmin). > >> > We advise to update your application to use the new style of APIs, > >> since > >> > deprecated APIs might be removed in future releases (2.x). See [2] > and > >> > [3] > >> > for an overview of changes. All Client side API's are marked with > >> > InterfaceAudience.Public class, indicating that the class/method is > an > >> > official "client API" for HBase. All 1.x releases are planned to be > >> API > >> > compatible for these classes. See [1] for an overview. > >> > > >> > Master runs a Region Server as well > >> > Starting with 1.0.0, the HBase master server and backup master > servers > >> > will > >> > also act as a region server. RPC port and info port for web UI is > >> shared > >> > for > >> > the master and region server roles. Active master can host regions > of > >> > defined tables if configured (disabled by default). Backup masters > >> will > >> > not > >> > host regions. > >> > > >> > Read availability using timeline consistent region replicas > >> > This release contains Phase 1 items for experimental "Read > >> availability > >> > using > >> > timeline consistent region replicas" feature. A region can be hosted > >> in > >> > multiple region servers in read-only mode. One of the replicas for > the > >> > region > >> > will be primary, accepting writes, and other replicas will be > sharing > >> > the same > >> > data files. Read requests can be done against any replica for the > >> region > >> > with > >> > backup RPCs for high availability with timeline consistency > >> guarantees. > >> > More > >> > information can be found at HBASE-10070. > >> > > >> > Online config change and other forward
[jira] [Created] (HBASE-12979) Use setters instead of return values for handing back statistics from HRegion methods
Andrew Purtell created HBASE-12979: -- Summary: Use setters instead of return values for handing back statistics from HRegion methods Key: HBASE-12979 URL: https://issues.apache.org/jira/browse/HBASE-12979 Project: HBase Issue Type: Improvement Affects Versions: 0.98.10 Reporter: Andrew Purtell Assignee: Andrew Purtell In HBASE-5162 (and backports such as HBASE-12729) we modified some HRegion methods to return statistics for consumption by callers. The statistics are ultimately passed back to the client as load feedback. [~lhofhansl] thinks returning this information is a weird mix of concerns. This also produced a difficult to anticipate binary compatibility issue with Phoenix. There was no compile time issue because the code of course was not structured to assign from a method returning void, yet the method signature changes so the JVM cannot resolve it if older Phoenix binaries are installed into a 0.98.10 release. Let's change the HRegion methods back to returning 'void' and use setters instead. Officially we don't support use of HRegion (HBASE-12566) but we do not need to go out of our way to break things (smile) so I would also like to make a patch release containing just this change to help out our sister project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-12978) hbase:meta has a row missing hregioninfo and it causes my long-running job to fail
stack created HBASE-12978: - Summary: hbase:meta has a row missing hregioninfo and it causes my long-running job to fail Key: HBASE-12978 URL: https://issues.apache.org/jira/browse/HBASE-12978 Project: HBase Issue Type: Bug Reporter: stack Fix For: 1.0.0 Testing 1.0.0 trying long-running tests. A row in hbase:meta was missing its HRI entry. It caused the job to fail. Around the time of the first task failure, there are balances of the hbase:meta region and it was on a server that crashed. I tried to look at what happened around time of our writing hbase:meta and I ran into another issue; 20 logs of 256MBs filled with WrongRegionException written over a minute or two. The actual update of hbase:meta was not in the logs, it'd been rotated off. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] Fourth release candidate for HBase 1.0.0 (RC3) is available. Please vote by Feb 11 2015
Did some more testing: Compiled Hive trunk against published maven artifacts Used shell to exercise various commands, including update_all_config command (verified by reloading regionserver:60030/conf) All looked good. On Tue, Feb 3, 2015 at 10:32 AM, Ted Yu wrote: > +1 based on the following: > > Checked signature > Ran test suite > Loaded tarball on a 5-node cluster > Ran LoadTestTool which passed > > Will continue testing. > > On Mon, Feb 2, 2015 at 5:11 PM, Enis Söztutar wrote: > >> To get the ball rolling, here are the tests that I have done so far. No >> official +1 yet, since I will spend some more time on this. >> >> - checked checksums, sigs >> - checked the bin and src artifacts >> - checked layouts >> - checked java files in src tarball, and jar files in bin tarball >> - checked the book and the site (they are new style) >> - checked javadocs for both devapi and userapi >> - checked reported version, build time, revision >> - run some smoke tests using shell >> - started local mode >> - run LTT local mode >> - checked the webUI in local mode >> - checked JMX dump and debug dump >> >> I had run most of the ITs on the other RC's, but I'll repeat them for this >> and report here when done. >> >> Happy testing, >> Enis >> >> On Sun, Feb 1, 2015 at 6:38 PM, Enis Söztutar wrote: >> >> > It gives me great pleasure to announce that the fourth release candidate >> > for the release >> > 1.0.0 (HBase-1.0.0RC3), is available for download at >> > https://dist.apache.org/repos/dist/dev/hbase/hbase-1.0.0RC3/ >> > >> > Maven artifacts are also available in the temporary repository >> > https://repository.apache.org/content/repositories/orgapachehbase-1061 >> > >> > Signed with my code signing key E964B5FF. Can be found here: >> > https://people.apache.org/keys/committer/enis.asc >> > >> > Signed tag in the repository can be found here: >> > >> > >> https://git-wip-us.apache.org/repos/asf?p=hbase.git;a=tag;h=46d9c29d83b535781e8fa8a044c12ee990a002c3 >> > >> > HBase 1.0.0 is the next stable release, and the start of "semantic >> > versioned" >> > releases (See [1]). >> > >> > The theme of 1.0.0 release is to become a stable base for future 1.x >> series >> > of releases. We aim to achieve at least the same level of stability of >> 0.98 >> > releases. >> > >> > 1.0.0 release contains 167 fixes on top of 0.99.2 release. Together with >> > the >> > previous 0.99.x releases, major changes in 1.0.0 are listed (but not >> > limited to) >> > below. Note that all previous 0.99.x releases are developer preview >> > releases, and will >> > NOT be supported in any form. >> > >> > API Cleanup and changes >> > 1.0.0 introduces new APIs, and deprecates some of commonly-used >> > client side APIs (HTableInterface, HTable and HBaseAdmin). >> > We advise to update your application to use the new style of APIs, >> since >> > deprecated APIs might be removed in future releases (2.x). See [2] and >> > [3] >> > for an overview of changes. All Client side API's are marked with >> > InterfaceAudience.Public class, indicating that the class/method is an >> > official "client API" for HBase. All 1.x releases are planned to be >> API >> > compatible for these classes. See [1] for an overview. >> > >> > Master runs a Region Server as well >> > Starting with 1.0.0, the HBase master server and backup master servers >> > will >> > also act as a region server. RPC port and info port for web UI is >> shared >> > for >> > the master and region server roles. Active master can host regions of >> > defined tables if configured (disabled by default). Backup masters >> will >> > not >> > host regions. >> > >> > Read availability using timeline consistent region replicas >> > This release contains Phase 1 items for experimental "Read >> availability >> > using >> > timeline consistent region replicas" feature. A region can be hosted >> in >> > multiple region servers in read-only mode. One of the replicas for the >> > region >> > will be primary, accepting writes, and other replicas will be sharing >> > the same >> > data files. Read requests can be done against any replica for the >> region >> > with >> > backup RPCs for high availability with timeline consistency >> guarantees. >> > More >> > information can be found at HBASE-10070. >> > >> > Online config change and other forward ports from 0.89-fb branch >> > HBASE-12147 forward ported online config change which enables some of >> the >> > configuration from the server to be reloaded without restarting the >> > region >> > servers. >> > >> > Other notable improvements in 1.0.0 (including previous 0.99.x) are >> > - A new web skin in time for 1.0 (http://hbase.apache.org) >> > - Automatic tuning of global memstore and block cache sizes >> > - Various security, tags and visibility labels improvements >> > - Bucket cache improvements (usability and compressed data blocks) >> > - A new pluggable replication endpoint to plug in to
[jira] [Resolved] (HBASE-12958) SSH doing hbase:meta get but hbase:meta not assigned
[
https://issues.apache.org/jira/browse/HBASE-12958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell resolved HBASE-12958.
Resolution: Fixed
Addendum pushed to 0.98
> SSH doing hbase:meta get but hbase:meta not assigned
>
>
> Key: HBASE-12958
> URL: https://issues.apache.org/jira/browse/HBASE-12958
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0, 1.0.1, 1.1.0, 0.98.11
>
> Attachments: 12958.txt, 12958v2.txt, 12958v2.txt,
> HBASE-12958-0.98-addendum.patch
>
>
> All master threads are blocked waiting on this call to return:
> {code}
> "MASTER_SERVER_OPERATIONS-c2020:16020-2" #189 prio=5 os_prio=0
> tid=0x7f4b0408b000 nid=0x7821 in Object.wait() [0x7f4ada24d000]
>java.lang.Thread.State: TIMED_WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at
> org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithRetries(RpcRetryingCaller.java:168)
> - locked <0x00041c374f50> (a
> java.util.concurrent.atomic.AtomicBoolean)
> at org.apache.hadoop.hbase.client.HTable.get(HTable.java:881)
> at
> org.apache.hadoop.hbase.MetaTableAccessor.get(MetaTableAccessor.java:208)
> at
> org.apache.hadoop.hbase.MetaTableAccessor.getRegionLocation(MetaTableAccessor.java:250)
> at
> org.apache.hadoop.hbase.MetaTableAccessor.getRegion(MetaTableAccessor.java:225)
> at
> org.apache.hadoop.hbase.master.RegionStates.serverOffline(RegionStates.java:634)
> - locked <0x00041c1f0d80> (a
> org.apache.hadoop.hbase.master.RegionStates)
> at
> org.apache.hadoop.hbase.master.AssignmentManager.processServerShutdown(AssignmentManager.java:3298)
> at
> org.apache.hadoop.hbase.master.handler.ServerShutdownHandler.process(ServerShutdownHandler.java:226)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:128)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Master is stuck trying to find hbase:meta on the server that just crashed and
> that we just recovered:
> Mon Feb 02 23:00:02 PST 2015, null, java.net.SocketTimeoutException:
> callTimeout=6, callDuration=68181: row '' on table 'hbase:meta' at
> region=hbase:meta,,1.1588230740,
> hostname=c2022.halxg.cloudera.com,16020,1422944918568, seqNum=0
> Will add more detail in a sec.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (HBASE-12958) SSH doing hbase:meta get but hbase:meta not assigned
[
https://issues.apache.org/jira/browse/HBASE-12958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell reopened HBASE-12958:
Patch application broke both 0.98 builds with compile errors. Please check
compile before commit, it doesn't take long. I will fix the problem this time.
> SSH doing hbase:meta get but hbase:meta not assigned
>
>
> Key: HBASE-12958
> URL: https://issues.apache.org/jira/browse/HBASE-12958
> Project: HBase
> Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: stack
>Assignee: stack
> Fix For: 2.0.0, 1.0.1, 1.1.0, 0.98.11
>
> Attachments: 12958.txt, 12958v2.txt, 12958v2.txt
>
>
> All master threads are blocked waiting on this call to return:
> {code}
> "MASTER_SERVER_OPERATIONS-c2020:16020-2" #189 prio=5 os_prio=0
> tid=0x7f4b0408b000 nid=0x7821 in Object.wait() [0x7f4ada24d000]
>java.lang.Thread.State: TIMED_WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at
> org.apache.hadoop.hbase.client.RpcRetryingCaller.callWithRetries(RpcRetryingCaller.java:168)
> - locked <0x00041c374f50> (a
> java.util.concurrent.atomic.AtomicBoolean)
> at org.apache.hadoop.hbase.client.HTable.get(HTable.java:881)
> at
> org.apache.hadoop.hbase.MetaTableAccessor.get(MetaTableAccessor.java:208)
> at
> org.apache.hadoop.hbase.MetaTableAccessor.getRegionLocation(MetaTableAccessor.java:250)
> at
> org.apache.hadoop.hbase.MetaTableAccessor.getRegion(MetaTableAccessor.java:225)
> at
> org.apache.hadoop.hbase.master.RegionStates.serverOffline(RegionStates.java:634)
> - locked <0x00041c1f0d80> (a
> org.apache.hadoop.hbase.master.RegionStates)
> at
> org.apache.hadoop.hbase.master.AssignmentManager.processServerShutdown(AssignmentManager.java:3298)
> at
> org.apache.hadoop.hbase.master.handler.ServerShutdownHandler.process(ServerShutdownHandler.java:226)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:128)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Master is stuck trying to find hbase:meta on the server that just crashed and
> that we just recovered:
> Mon Feb 02 23:00:02 PST 2015, null, java.net.SocketTimeoutException:
> callTimeout=6, callDuration=68181: row '' on table 'hbase:meta' at
> region=hbase:meta,,1.1588230740,
> hostname=c2022.halxg.cloudera.com,16020,1422944918568, seqNum=0
> Will add more detail in a sec.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (HBASE-12914) Mark public features that require HFilev3 Unstable in 0.98, warn in upgrade section
[ https://issues.apache.org/jira/browse/HBASE-12914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell resolved HBASE-12914. Resolution: Fixed My bad, the Jenkins changelog lead me astray, the issue is the HBASE-12958 commit. I am going to go make the above comment over there. > Mark public features that require HFilev3 Unstable in 0.98, warn in upgrade > section > --- > > Key: HBASE-12914 > URL: https://issues.apache.org/jira/browse/HBASE-12914 > Project: HBase > Issue Type: Bug > Components: API, documentation >Affects Versions: 0.98.6, 0.98.7, 0.98.8, 0.98.9 >Reporter: Sean Busbey >Assignee: ramkrishna.s.vasudevan >Priority: Critical > Fix For: 0.98.11 > > Attachments: HBASE-12914-0.98.patch, HBASE-12914-branch-1.patch, > HBASE-12914.patch > > > There are several features in 0.98 that require enabling HFilev3 support. > Some of those features include new extendable components that are marked > IA.Public. > Current practice has been to treat these features as experimental. This has > included pushing non-compatible changes to branch-1 as the API got worked out > through use in 0.98. > * Update all of the IA.Public classes involved to make sure they are > IS.Unstable in 0.98. > * Update the ref guide section on upgrading from 0.98 -> 1.0 to make folks > aware of these changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (HBASE-12914) Mark public features that require HFilev3 Unstable in 0.98, warn in upgrade section
[ https://issues.apache.org/jira/browse/HBASE-12914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell reopened HBASE-12914: Patch application broke both 0.98 builds with compile errors. Please check compile before commit, it doesn't take long. I will fix the problem this time. > Mark public features that require HFilev3 Unstable in 0.98, warn in upgrade > section > --- > > Key: HBASE-12914 > URL: https://issues.apache.org/jira/browse/HBASE-12914 > Project: HBase > Issue Type: Bug > Components: API, documentation >Affects Versions: 0.98.6, 0.98.7, 0.98.8, 0.98.9 >Reporter: Sean Busbey >Assignee: ramkrishna.s.vasudevan >Priority: Critical > Fix For: 0.98.11 > > Attachments: HBASE-12914-0.98.patch, HBASE-12914-branch-1.patch, > HBASE-12914.patch > > > There are several features in 0.98 that require enabling HFilev3 support. > Some of those features include new extendable components that are marked > IA.Public. > Current practice has been to treat these features as experimental. This has > included pushing non-compatible changes to branch-1 as the API got worked out > through use in 0.98. > * Update all of the IA.Public classes involved to make sure they are > IS.Unstable in 0.98. > * Update the ref guide section on upgrading from 0.98 -> 1.0 to make folks > aware of these changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [RESULT] [VOTE] The 3rd HBase 0.98.10 release candidate (RC2) is available, vote closing 2/4/2015
Don't let me forget to thank all who voted on the release! (Doh) Your patience and time are really appreciated. On Thu, Feb 5, 2015 at 10:15 AM, Andrew Purtell wrote: > With 4 +1 votes and no votes <= 0, the vote passes and we have our 0.98.10 > release. I have sent the artifacts onward for distribution and will send > out the release announcement shortly. > > > On Sat, Jan 31, 2015 at 10:07 PM, Andrew Purtell > wrote: > >> The 3rd HBase 0.98.10 release candidate (RC2) is available for >> download at http://people.apache.org/~apurtell/0.98.10RC2/ and Maven >> artifacts are also available in the temporary repository >> https://repository.apache.org/content/repositories/orgapachehbase-1060/ >> >> Signed with my code signing key D5365CCD. >> >> The issues resolved in this release can be found at >> http://s.apache.org/7hO >> >> Please try out the candidate and vote +1/-1 by midnight Pacific Time >> (00:00 -0800 GMT) on February 4 on whether or not we should release this >> as 0.98.10. Three +1 votes from PMC will be required to release. >> > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
[RESULT] [VOTE] The 3rd HBase 0.98.10 release candidate (RC2) is available, vote closing 2/4/2015
With 4 +1 votes and no votes <= 0, the vote passes and we have our 0.98.10 release. I have sent the artifacts onward for distribution and will send out the release announcement shortly. On Sat, Jan 31, 2015 at 10:07 PM, Andrew Purtell wrote: > The 3rd HBase 0.98.10 release candidate (RC2) is available for > download at http://people.apache.org/~apurtell/0.98.10RC2/ and Maven > artifacts are also available in the temporary repository > https://repository.apache.org/content/repositories/orgapachehbase-1060/ > > Signed with my code signing key D5365CCD. > > The issues resolved in this release can be found at > http://s.apache.org/7hO > > Please try out the candidate and vote +1/-1 by midnight Pacific Time > (00:00 -0800 GMT) on February 4 on whether or not we should release this > as 0.98.10. Three +1 votes from PMC will be required to release. >
[jira] [Resolved] (HBASE-12977) normalize handlerCount to keep handlers distributed evenly among callQueues
[ https://issues.apache.org/jira/browse/HBASE-12977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell resolved HBASE-12977. Resolution: Not a Problem Assignee: (was: hongyu bi) Resolving as Not A Problem, please reopen if you disagree with the outcome > normalize handlerCount to keep handlers distributed evenly among callQueues > > > Key: HBASE-12977 > URL: https://issues.apache.org/jira/browse/HBASE-12977 > Project: HBase > Issue Type: Improvement >Reporter: hongyu bi >Priority: Minor > Attachments: HBASE-12977-v0.patch > > > If enable multi callQueues , handlers may not be distributed evenly among > multi queues, which mean the queue's capacity is not the same. Should we make > handler's distribution even? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-12977) normalize handlerCount to keep handlers distributed evenly among callQueues
hongyu bi created HBASE-12977: - Summary: normalize handlerCount to keep handlers distributed evenly among callQueues Key: HBASE-12977 URL: https://issues.apache.org/jira/browse/HBASE-12977 Project: HBase Issue Type: Improvement Reporter: hongyu bi Assignee: hongyu bi Priority: Minor If enable multi callQueues , handlers may not be distributed evenly among multi queues, which mean the queue's capacity is not the same. Should we make handler's distribution even? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
