Re: Query for OldWals and use of WAl for Hbase indexer

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

Re: Query for OldWals and use of WAl for Hbase indexer

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

Re: Query for OldWals and use of WAl for Hbase indexer

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

Re: Query for OldWals and use of WAl for Hbase indexer

Hi Reid You suggest me to directly delete OldWals by using Hdfs command "hdfs -rm" Question is : It's really safe and I will not lose any data and Indexing from the system. Thanks Manjeet Singh On Thu, Jul 12, 2018 at 12:09 PM, Manjeet Singh wrote: > Hi > > I have created HBASE-20877 >

Re: Query for OldWals and use of WAl for Hbase indexer

Hi I have created HBASE-20877 for the same, request you to please move it into active sprint. Thanks Manjeet Singh On Thu, Jul 12, 2018 at 7:42 AM, Reid Chan wrote: > oldWals are supposed to be cleaned in master background chore, I also >

Re: Query for OldWals and use of WAl for Hbase indexer

oldWals are supposed to be cleaned in master background chore, I also doubt they are needed. HBASE-20352(for 1.x version) is to speed up cleaning oldWals, it may address your concern "OldWals is quite huge" R.C From: Manjeet Singh Sent: 12 July

Re: Query for OldWals and use of WAl for Hbase indexer

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? Thanks Manjeet singh On Wed, 11 Jul 2018, 23:19 Manjeet Singh, wrote: > Thanks Sean for your reply > > I still have some

Re: Query for OldWals and use of WAl for Hbase indexer

Thanks Sean for your reply I still have some question un answered like Q1: How Hbase syncronized with Hbase indexer. Q2 What optimization I can apply. Q3 As it's clear from my stats, data in OldWals is quite huge so it's not getting clear my HMaster., how can I improve my HDFS space issue due to

Re: Query for OldWals and use of WAl for Hbase indexer

Presuming you're using the Lily indexer[1], yes it relies on hbase's built in cross-cluster replication. The replication system stores WALs until it can successfully send them for replication. If you look in ZK you should be able to see which regionserver(s) are waiting to send those WALs over.

Query for OldWals and use of WAl for Hbase indexer

Hi All I have a query regarding Hbase replication and OldWals Hbase version 1.2.1 To enable Hbase indexing we use below command on table alter '', {NAME => 'CF1', REPLICATION_SCOPE => 1} By Doing this actually replication get enabled as hbase-indexer required it, as per my understanding