Is your cluster under heavy write load when you see these expceptions? How long does it take to write a batch of mutations? If its longer than the config value of maxServerCacheTimeToLiveMs you will see the exception because the index metadata expired from the cache.
On Sun, Sep 2, 2018 at 4:02 PM, Batyrshin Alexander <0x62...@gmail.com> wrote: > Hello all, > We use mutable table with many indexes on it. On upserts we getting this > error: > > o.a.phoenix.execute.MutationState - Swallowing exception and retrying > after clearing meta cache on connection. java.sql.SQLException: ERROR 2008 > (INT10): Unable to find cached index metadata. ERROR 2008 (INT10): ERROR > 2008 (INT10): Unable to find cached index metadata. key=8283602185356160420 > region=HISTORY,D\xEF\xBF\xBD\xEF\xBF\xBDNt\x1B\xEF\xBF\xBD\ > xEF\xBF\xBD\xEF\xBF\xBD5\x1E\x01W\x02\xEF\xBF\xBD$,1531781097243. > 95d19923178a7d80fa55428b97816e3f.host=cloud016,60020,1535926087741 Index > update failed > > > Current config: > phoenix-4.14.0-HBase-1.4 > phoenix.coprocessor.maxServerCacheTimeToLiveMs = 60000 > ALTER TABLE HISTORY SET UPDATE_CACHE_FREQUENCY=60000
