Re: Dropping of Index can still leave some non-replayed writes Phoenix-2915

This didn't work Ankit. Please find below detailed logs on region server. Please let me know what else I can try. When I try to run hbck command, this is the error I get: ERROR: There is a hole in the region chain between \x06 and \x07. You need to create a new .regioninfo and region dir in hdfs

Re: linkage error using Groovy

Any luck with this? > On Jun 9, 2016, at 10:07 PM, Josh Elser wrote: > > FWIW, I've also reproduced this with Groovy 2.4.3, Oracle Java 1.7.0_79 and > Apache Phoenix 4.8.0-SNAPSHOT locally. > > Will dig some more. > > Brian Jeltema wrote: >> Groovy 2.4.3 >> JDK 1.8 >>

Re: Dropping of Index can still leave some non-replayed writes Phoenix-2915

Yes, restart your cluster On Wed, Jun 15, 2016 at 8:17 AM, anupama agarwal wrote: > I have created async index with same name. But I am still getting the same > error. Should I restart my cluster for changes to reflect? > On Jun 15, 2016 8:38 PM, "Ankit Singhal"

Re: Dropping of Index can still leave some non-replayed writes Phoenix-2915

Hi Anupama, Option 1:- You can create a ASYNC index so that WAL can be replayed. And once your regions are up , remember to do the flush of data table before dropping the index. Option 2:- Create a table in hbase with the same name as index table name by using hbase shell. Regards, Ankit