[jira] [Created] (HBASE-5846) HBase rpm packing is broken at multiple places
HBase rpm packing is broken at multiple places
--
Key: HBASE-5846
URL: https://issues.apache.org/jira/browse/HBASE-5846
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.92.1
Environment: CentOS release 5.7 (Final)
Reporter: Shrijeet Paliwal
Here is how I executed rpm build:
{noformat}
MAVEN_OPTS=-Xmx2g mvn clean package assembly:single -Prpm -DskipTests
{noformat}
The issues with the rpm build are:
* There is no clean (%clean) section in the hbase.spec file . Last run can
leave stuff in RPM_BUILD_ROOT which in turn will fail build. As a fix I added
'rm -rf $RPM_BUILD_ROOT' to %clean section
* The Buildroot is set to _build_dir . The build fails with this error.
{noformat}
cp: cannot copy a directory,
`/data/9adda425-1f1e-4fe5-8a53-83bd2ce5ad45/app/jenkins/workspace/hbase.92/target/rpm/hbase/BUILD',
into itself,
`/data/9adda425-1f1e-4fe5-8a53-83bd2ce5ad45/app/jenkins/workspace/hbase.92/target/rpm/hbase/BUILD/BUILD'
{noformat}
If we set it to ' %{_tmppath}/%{name}-%{version}-root' build passes
* The src/packages/update-hbase-env.sh script will leave inconsistent state if
'yum update hbase' is executed. It deletes data from /etc/init.d/hbase* and
does not put scripts back during update.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-5779) Master goes to infinite loop if AccessControlException occurs while setting cluster id during initialization
Master goes to infinite loop if AccessControlException occurs while setting
cluster id during initialization
-
Key: HBASE-5779
URL: https://issues.apache.org/jira/browse/HBASE-5779
Project: HBase
Issue Type: Bug
Affects Versions: 0.92.1
Reporter: Shrijeet Paliwal
Steps to reproduce:
- change permission of /hbase to a user other than one running hbase
- delete hbase.id if already exists
- start master, it will try to create cluster ID file in /hbase and fail while
doing so with org.apache.hadoop.security.AccessControlException
From this point it will go to infinite loop.
Reason: org.apache.hadoop.hbase.util.FSUtils.setClusterId has a wait 0 and
no control over retries when called during master initialization.
Quoting : checkRootDir in MasterFileSystem
{noformat}
// Make sure cluster ID exists
if (!FSUtils.checkClusterIdExists(fs, rd, c.getInt(
HConstants.THREAD_WAKE_FREQUENCY, 10 * 1000))) {
FSUtils.setClusterId(fs, rd, UUID.randomUUID().toString(), c.getInt(
HConstants.THREAD_WAKE_FREQUENCY, 10 * 1000));
}
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-5585) Add a feature in shell to allow adding entries into META easily
Add a feature in shell to allow adding entries into META easily
---
Key: HBASE-5585
URL: https://issues.apache.org/jira/browse/HBASE-5585
Project: HBase
Issue Type: Improvement
Components: shell
Reporter: Shrijeet Paliwal
Priority: Minor
From IRC
{noformat}
sulabhc St^Ack: that fixed most of the issue, just one last question, I removed
some META entries how do I put it back ?
sulabhc St^Ack: putting from Hbase-shell does not seem to be possible
St^Ack sulabhc: it is but the content in .META. is serialized Writable of
HRegionInfo.
St^Ack Can you find the region in the fs that you want to put back?
St^Ack If so, cat its .regioninfo
St^Ack it has binary format of the HRegionInfo that needs to be in .META. and
a txt version.
St^Ack You'll need to create an HRegionInfo, serialize it as bytes, and then
put that into .META.
St^Ack Look around in the catalog package, the MetaEditor class, for how to do
this from java.
St^Ack We should really make this easier to do in shell...
St^Ack or look in bin to see how we do some of this via (j)ruby
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-5582) No HServerInfo found for should be a WARNING message
No HServerInfo found for should be a WARNING message
--
Key: HBASE-5582
URL: https://issues.apache.org/jira/browse/HBASE-5582
Project: HBase
Issue Type: Improvement
Components: master
Affects Versions: 0.90.4
Reporter: Shrijeet Paliwal
Priority: Trivial
The message from RegionServerTracker No HServerInfo found for... is easy to
miss. It should not be INFO.
From irc chat
{noformat}
jdcryans
JohnP789: can you grep for No HServerInfo found for in that log?
jdcryans
wait I see it
jdcryans
ok there's your problem
shrijeet_
Yes it is there
shrijeet_
jdcryans: it should be INFO, why?
jdcryans
it shouldn't be INFO, it's so easy to miss
jdcryans
it's not the first time we have to look super closely to figure this one out
shrijeet_
yes , I will file a jira
jdcryans
in any case it's a mismatch in that machine's DNS config
shrijeet_
anyways JohnP789 is waiting :) go on
JohnP789
haha!
JohnP789
yes... ??? :-)
jdcryans
the master is expecting a RS called localhost.localdomain,53875,1328924863478
17:26 jdcryans
but the RS calls itself localhost,53875,1328924863478
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-5080) Make HConnectionManager's prefetchRegionCache error trace more helpful
Make HConnectionManager's prefetchRegionCache error trace more helpful -- Key: HBASE-5080 URL: https://issues.apache.org/jira/browse/HBASE-5080 Project: HBase Issue Type: Sub-task Components: client Affects Versions: 0.90.3 Reporter: Shrijeet Paliwal Priority: Minor We catch RuntimeException in this HConnectionManager's prefetchRegionCache method. The trace is not very helpful since it eats the information about the line where RuntimeException actually happened. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-5041) Major compaction on non existing table does not throw error
Major compaction on non existing table does not throw error
Key: HBASE-5041
URL: https://issues.apache.org/jira/browse/HBASE-5041
Project: HBase
Issue Type: Bug
Components: regionserver, shell
Affects Versions: 0.90.3
Reporter: Shrijeet Paliwal
Following will not complain even if fubar does not exist
{code}
echo major_compact 'fubar' | $HBASE_HOME/bin/hbase shell
{code}
The downside for this defect is that major compaction may be skipped due to
a typo by Ops.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-5035) Runtime exceptions during meta scan
Runtime exceptions during meta scan --- Key: HBASE-5035 URL: https://issues.apache.org/jira/browse/HBASE-5035 Project: HBase Issue Type: Bug Components: client Affects Versions: 0.90.3 Reporter: Shrijeet Paliwal Version: 0.90.3 + patches back ported The other day our client started spitting these two runtime exceptions. Not all clients connected to the cluster were under impact. Only 4 of them. While 3 of them were throwing NPE, one of them was throwing ArrayIndexOutOfBoundsException. The errors are : 1. http://pastie.org/2987926 2. http://pastie.org/2987927 Clients did not recover from this and I had to restart them. Motive of this jira is to identify and put null checks at appropriate places. Also with the given stack trace I can not tell which line caused NPE of AIOBE, hence additional motive is to make the trace more helpful. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-4980) Null pointer exception in HBaseClient receiveResponse
Null pointer exception in HBaseClient receiveResponse
-
Key: HBASE-4980
URL: https://issues.apache.org/jira/browse/HBASE-4980
Project: HBase
Issue Type: Bug
Components: client
Affects Versions: 0.92.0
Reporter: Shrijeet Paliwal
Relevant Stack trace:
2011-11-30 13:10:26,557 [IPC Client (47) connection to
xx.xx.xx/172.22.4.68:60020 from an unknown user] WARN
org.apache.hadoop.ipc.HBaseClient - Unexpected exception receiving call
responses
java.lang.NullPointerException
-at
org.apache.hadoop.hbase.ipc.HBaseClient$Connection.receiveResponse(HBaseClient.java:583)
-at
org.apache.hadoop.hbase.ipc.HBaseClient$Connection.run(HBaseClient.java:511)
{code}
if (LOG.isDebugEnabled())
LOG.debug(getName() + got value # + id);
Call call = calls.remove(id);
// Read the flag byte
byte flag = in.readByte();
boolean isError = ResponseFlag.isError(flag);
if (ResponseFlag.isLength(flag)) {
// Currently length if present is unused.
in.readInt();
}
int state = in.readInt(); // Read the state. Currently unused.
if (isError) {
//noinspection ThrowableInstanceNeverThrown
call.setException(new RemoteException( WritableUtils.readString(in),
WritableUtils.readString(in)));
} else {
{code}
This line {code}Call call = calls.remove(id);{code} may return a null 'call'.
It is so because if you have rpc timeout enable, we proactively clean up other
calls which have expired their lifetime along with the call for which socket
timeout exception happend.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HBASE-4633) Potential memory leak in client RPC timeout mechanism
Potential memory leak in client RPC timeout mechanism - Key: HBASE-4633 URL: https://issues.apache.org/jira/browse/HBASE-4633 Project: HBase Issue Type: Bug Components: client Affects Versions: 0.90.3 Environment: HBase version: 0.90.3 + Patches , Hadoop version: CDH3u0 Reporter: Shrijeet Paliwal Relevant Jiras: https://issues.apache.org/jira/browse/HBASE-2937, https://issues.apache.org/jira/browse/HBASE-4003 We have been using the 'hbase.client.operation.timeout' knob introduced in 2937 for quite some time now. It helps us enforce SLA. We have two HBase clusters and two HBase client clusters. One of them is much busier than the other. We have seen a deterministic behavior of clients running in busy cluster. Their (client's) memory footprint increases consistently after they have been up for roughly 24 hours. This memory footprint almost doubles from its usual value (usual case == RPC timeout disabled). After much investigation nothing concrete came out and we had to put a hack which keep heap size in control even when RPC timeout is enabled. Also note , the same behavior is not observed in 'not so busy cluster. The patch is here : https://gist.github.com/1288023 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
