e 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 (INT1
.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
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
obal, the data table has more than a 100B rows
>
> 2016-11-26 12:15:41,250 INFO
> [RW.default.writeRpcServer.handler=40,queue=6,port=16020]
> util.IndexManagementUtil: Rethrowing
> org.apache.hadoop.hbase.DoNotRetryIOException: ERROR 2008 (INT10): ERROR
>
,queue=6,port=16020]
util.IndexManagementUtil: Rethrowing
org.apache.hadoop.hbase.DoNotRetryIOException: ERROR 2008 (INT10): ERROR
2008 (INT10): Unable to find cached index metadata.
key=7015231383024113337 region=,-056946674
,1477336770695.07d70ebd63f737a62e24387cf0912af5. Index
update
o 360. This still does not help and we keep
>>>> seeing this once in a while. What's not clear is also if this setting is
>>>> relevant for client or just the server.
>>>>
>>>> Any help is appreciated
>>>>
>>>> org.ap
tting is
>>> relevant for client or just the server.
>>>
>>> Any help is appreciated
>>>
>>> org.apache.phoenix.execute.CommitException: java.sql.SQLException: ERROR
>>> 2008 (INT10)
s not clear is also if this setting is relevant
>> for client or just the server.
>>
>> Any help is appreciated
>>
>> org.apache.phoenix.execute.CommitException: java.sql.SQLException: ERROR
>> 2008 (INT10): Unable to find cached index metadata. ERROR 2008 (
What's not clear is also if this setting is relevant for
> client or just the server.
>
> Any help is appreciated
>
> org.apache.phoenix.execute.CommitException: java.sql.SQLException: ERROR 2008
> (INT10): Unable to find cached index metadata. ERROR 2008 (INT10): ERROR
> 2008
ave created a global secondary in one table. I
>> am running MapReduce job with 20 reducers to load data into this
>> table(maybe i m doing 50 writes/second/reducer). Dataset is around 500K
>> rows only. My mapreduce job is failing due to this exception:
>> Caused by: org.apache.ph
My mapreduce job is failing due to this exception:
> Caused by: org.apache.phoenix.execute.CommitException:
> 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=-4135398719
es/second/reducer). Dataset is around 500K rows only. My
> mapreduce job is failing due to this exception:
> Caused by: org.apache.phoenix.execute.CommitException: java.sql.SQLException:
> ERROR 2008 (INT10): Unable to find cached index metadata. ERROR 2008
> (INT10): ERROR 2008 (INT10
...@certusnet.com.cn [su...@certusnet.com.cn]
Sent: Tuesday, September 02, 2014 8:27 AM
To: user
Subject: Re: Re: Unable to find cached index metadata
Hi,
Thanks for your reply. Sorry for not completely describing my job
information.
I had configured the properties in hbase-site.xml in hmaster node
()’
//hbaseUpsertExecutor.executeBatch()
//stmt.execute();
}
hbaseUpsertExecutor.executeBatch()
// connection.setAutoCommit(false);
conn.commit(); // here got the error message. ERROR
2008 (INT10): Unable to find cached index metadata.
// logger.info( inserted batch + batchIndex
14 matches
Mail list logo
