phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Soldatov (JIRA)" <j...@apache.org>
Subject [jira] [Created] (PHOENIX-4224) Automatic resending cache for HashJoin when cache has expired on server side doesn't work
Date Fri, 22 Sep 2017 06:34:00 GMT
Sergey Soldatov created PHOENIX-4224:
----------------------------------------

             Summary: Automatic resending cache for HashJoin when cache has expired on server
side doesn't work
                 Key: PHOENIX-4224
                 URL: https://issues.apache.org/jira/browse/PHOENIX-4224
             Project: Phoenix
          Issue Type: Bug
    Affects Versions: 4.12.0
            Reporter: Sergey Soldatov
            Assignee: Sergey Soldatov
            Priority: Blocker
             Fix For: 4.12.0


The problem occurs when the cache has expired on server side and client want to resend it.
This problem has been introduced in PHOENIX-4010. Actual result in this case is that client
doesn't send the cache because of the following check:
{noformat}
			if (cache.addServer(tableRegionLocation) ... )) {
				success = addServerCache(table, startkeyOfRegion, pTable, cacheId, cache.getCachePtr(),
cacheFactory, txState);
			}
{noformat}
Since the region location hasn't been changed, we actually don't send cache again, but produce
new scanner which will fail with the same error and client will fall to recursion. 




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message