[
https://issues.apache.org/jira/browse/OMID-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16807285#comment-16807285
]
Lars Hofhansl commented on OMID-140:
------------------------------------
To reproduce with Phoenix:
# create table test (pk1 integer not null, pk2 integer not null, pk3 integer
not null, v1 float, v2 float, v3 integer CONSTRAINT pk PRIMARY KEY (pk1, pk2,
pk3)) DISABLE_WAL=true, TRANSACTIONAL=true;
# upsert into test values(rand()*10000000, rand()*10000000, rand()*10000000,
rand(), rand(), rand()*1000000);
# upsert into test select rand()*10000000, rand()*10000000, rand()*10000000,
rand(), rand(), rand()*1000000 from test;
# goto 3. until you see this error.
> ServiceUnavailableException when the write set if is too large.
> ---------------------------------------------------------------
>
> Key: OMID-140
> URL: https://issues.apache.org/jira/browse/OMID-140
> Project: Apache Omid
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Priority: Major
>
> In the debugger I see this:
> {code}
> java.util.concurrent.ExecutionException:
> org.apache.omid.tso.client.ServiceUnavailableException: Number of retries
> exceeded. This API request failed permanently
> {code}
> {code}
> Thrown from here:
> HBaseTransactionManager(AbstractTransactionManager).commitRegularTransaction(AbstractTransaction<CellId>)
> line: 417
> HBaseTransactionManager(AbstractTransactionManager).commit(Transaction) line:
> 252
> OmidTransactionContext.commit() line: 124
> MutationState.commit() line: 1226
> PhoenixConnection$3.call() line: 673
> PhoenixConnection$3.call() line: 669
> CallRunner.run(T, CallWrapper...) line: 53
> PhoenixConnection.commit() line: 669
> {code}
> In my case I tried with a write set of 2^20 (a bit over 1m) rows. And in my
> case with 4m cells.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
