I try to build HBase 2.1.5
error is..
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.EvaluateBeanshell failed
with message:
License errors detected, for more detail find ERROR in
/ws/build/hbase2/rpm/BUILD/hbase-2.1.5-src/hbase-shaded/hbase-shaded-client/target/maven-sha
As a project we can't speak on what your risk tolerance is for open
source licensing.
what HBase version are you trying to build from source? what's the
specific error reported in the LICENSE file?
probably the particular Hadoop version you are building added some new
dependency that we haven't a
>
> Maybe the readRequests counter increments for each row read during a
> scanNext call ?
Correct!!
https://github.com/apache/hbase/blob/rel/1.2.12/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RSRpcServices.java#L2672
https://github.com/apache/hbase/blob/rel/1.2.12/hbase-server
Hello, User.
While I build HBase from the source. I got an error that is License errors
detected, for more detail find ERROR in
/hbase-shaded/hbase-shaded-client/target/maven-shared-archive-resources/META-INF/LICENSE.
My build environment is CentOS 6.3
Command is mvn -DskipTests -Dslf4j.version
If you are using region replication, then you might be hitting
https://issues.apache.org/jira/browse/HBASE-21644
Thanks,
Ankit Singhal
On Fri, Jul 5, 2019 at 9:53 AM Stack wrote:
> Looks like known issue. Can you update to later branch-2.0 release or patch
> what you have?
> Thanks,
> S
>
> On
I see your point. I won't disable_peer right away after I add new one. Will
wait for data to replicate and make sure there's no lag.
Thanks!
--
Sent from: http://apache-hbase.679495.n3.nabble.com/HBase-User-f4020416.html
> I won't miss any data as long as I add_peer (step 1) before I
disable_peer (step 2).
Yes, Wellington is right.
Consider the case:
1. hlog1 enqueued in ORIGAL_ID peer;
2. rs roll to write hlog2;
3. add the new peer (your step#1) with NEW_ID, it will only enqueue the
hlog2 to NEW_ID peer;
4.
Hi Marjana,
I guess OpenInx (much valid) point here is that between step#2 and #3, you
need to make sure there's no lags for ORIGINAL_PEER_ID, because if it has
huge lags, it might be that some of the edits pending on its queue came
before you added NEW_PEER_ID in step #1. In that case, since
ORIG
Hi OpenInx,
Correct, only ZK is being moved, hbase slave stays the same. I moved that
earlier effortlessly.
In order to move ZK, I will have to stop hbase. While it's down, hlogs will
accumulate for the NEW_ID and ORIGINAL_ID peers. Once I start hbase, hlogs
for NEW_ID will start replicating. hlogs
Sorry, seems I misunderstood your question. only zk configs change for
your slave cluster, the hbase slave cluster
keep the same.
Considered the steps your list:
1. add_peer NEW_ID 'newZK'
2. disable_peer ORIGINAL_ID 'originalZK'.
3. stop slave hbase. move ZK.
4. start slave hbase. Data starts c
10 matches
Mail list logo
