Re: java.io.IOException: Added a key not lexically larger than previous

2019-08-26 Thread Alexander Batyrshin
Looks like problem begun with 4.14.2 Maybe somehow https://issues.apache.org/jira/browse/PHOENIX-5266 can re-apply mutations to main table with bugs? > On 20 Jun 2019, at 04:16, Alexander Batyrshin <0x62...@gmail.com> wrote: > > Hello, > Are

Re: java.io.IOException: Added a key not lexically larger than previous

2019-08-15 Thread Alexander Batyrshin
> Since you're using a global index, which stores the index data in a separate > table (and hence different regions, each of which has a different MemStore / > set of HFiles), and the error's happening to the base table, I'd be surprised > if Phoenix indexing is related. AFAIK Phoenix handle

Re: java.io.IOException: Added a key not lexically larger than previous

2019-08-15 Thread Geoffrey Jacoby
Alexander, I can tell you what's happening but I don't know why. When you do a Put in HBase (which is what Phoenix UPSERTs do underneath), it gets committed to a mutable in-memory buffer called the MemStore. Periodically, the MemStore is flushed to a physical HDFS file called an HFile. The rule

Re: java.io.IOException: Added a key not lexically larger than previous

2019-08-15 Thread Alexander Batyrshin
> On 15 Aug 2019, at 21:27, Josh Elser wrote: > > Short-answer, it's possible that something around secondary indexing in > Phoenix causes this but not possible to definitively say in a vaccuum. As I see region-server crashes on main table (not index) memstore flush. How can I help to

Re: java.io.IOException: Added a key not lexically larger than previous

2019-08-15 Thread Alexander Batyrshin
Im using global index. HBase-1.4.10 Phoenix-4.14.2 I constantly get this issues today after increasing write load. > On 15 Aug 2019, at 21:27, Josh Elser wrote: > > Are you using a local index? Can you share the basics please (HBase and > Phoenix versions). > > I'm not seeing if you've

Re: java.io.IOException: Added a key not lexically larger than previous

2019-08-15 Thread Josh Elser
Are you using a local index? Can you share the basics please (HBase and Phoenix versions). I'm not seeing if you've shared this previously on this or another thread. Sorry if you have. Short-answer, it's possible that something around secondary indexing in Phoenix causes this but not

Re: java.io.IOException: Added a key not lexically larger than previous

2019-08-15 Thread Alexander Batyrshin
Is is possible that Phoenix is the reason of this problem? > On 20 Jun 2019, at 04:16, Alexander Batyrshin <0x62...@gmail.com> wrote: > > Hello, > Are there any ideas where this problem comes from and how to fix? > > Jun 18 21:38:05 prod022 hbase[148581]: 2019-06-18 21:38:05,348 WARN >