Please check the comments i leave in your filed jira.
From: Manjeet Singh
Sent: 12 July 2018 14:55:40
To: user@hbase.apache.org
Subject: Re: Query for OldWals and use of WAl for Hbase indexer
Hi
Reid
You suggest me to directly delete OldWals by using Hdf
I've got a question on the number of column families. I've told everyone
for years that you shouldn't use more than maybe 3-10 column families.
Our book still says the following:
"HBase currently does not do well with anything above two or three column
families so keep the number of column familie
Yes, Reid, every machine has specific keytab and corresponding principal.
On Wed, Jul 11, 2018 at 3:29 PM, Reid Chan wrote:
> Does every machine where hbase client runs has your specific keytab and
> corresponding principal?
>
> From snippet, i can tell that you're using service principal to lo
On Wed, Jul 11, 2018 at 7:19 PM, Manjeet Singh
wrote:
> I have one more question
>
> If solr is having its own data mean its maintaining data in their shards
> and hbase is maintaining in data folder... Why still oldWals need?
Once the HBase replication system is active and there's a peer (even
On Wed, Jul 11, 2018 at 12:49 PM, Manjeet Singh
wrote:
> Thanks Sean for your reply
>
> I still have some question un answered like
> Q1: How Hbase syncronized with Hbase indexer.
The Lily Indexer for HBase (sometimes referred to as the "Lily HBase
Indexer") is an independent project, linked to i
I think there's possibility that some of the clients login failed.
Have you tried checking your krb5kdc.log to see login audit, or turn on
-Dsun.security.krb5.debug=true?
And based on your situation, i suggest to use UPN(User Principal Name) with
format "name@REALM" instead of SPN.
R.C
__
