Looks like lock goes away 30 minutes after index region split.
So i can assume that this issue comes from cache that configured by this
option: phoenix.coprocessor.maxMetaDataCacheTimeToLiveMs
> On 21 Sep 2018, at 00:15, Batyrshin Alexander <0x62...@gmail.com> wrote:
>
> And how this split
And how this split looks at Master logs:
Sep 20 19:45:04 prod001 hbase[10838]: 2018-09-20 19:45:04,888 INFO
[AM.ZK.Worker-pool5-t282] master.RegionStates: Transition
{3e44b85ddf407da831dbb9a871496986 state=OPEN, ts=1537304859509,
server=prod013,60020,1537304282885} to
Looks like problem was because of index region split
Index region split at prod013:
Sep 20 19:45:05 prod013 hbase[193055]: 2018-09-20 19:45:05,441 INFO
[regionserver/prod013/10.0.0.13:60020-splits-1537400010677]
regionserver.SplitRequest: Region split, hbase:meta updated, and report to
Our setup:
HBase-1.4.7
Phoenix-4.14-hbase-1.4
> On 20 Sep 2018, at 20:19, Batyrshin Alexander <0x62...@gmail.com> wrote:
>
> Hello,
> Looks live we got dead lock with repeating "ERROR 1120 (XCL20)" exception. At
> this time all indexes is ACTIVE.
> Can you help to make deeper diagnose?
>
>
phoenix.mutate.maxSize
25
Try reducing the value of the above property, not sure if the size of your
row is more than 4MB(phoenix.mutate.maxSizeBytes/phoenix.mutate.maxSize) or
it's a bug or your configuration is not picked up.
Please raise a bug if changing the configuration didn't help.
Nope, it was client side config.
Thank you for response.
> On 20 Sep 2018, at 05:36, Jaanai Zhang wrote:
>
> Are you configuring these on the server side? Your “UPSERT SELECT” grammar
> will be executed on the server side.
>
>
>Jaanai Zhang
>
Hello,
Looks live we got dead lock with repeating "ERROR 1120 (XCL20)" exception. At
this time all indexes is ACTIVE.
Can you help to make deeper diagnose?
java.sql.SQLException: ERROR 1120 (XCL20): Writes to table blocked until index
can be updated. tableName=TBL_MARK
at
