phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-4165) Do not wait no new memory chunk can be allocated
Date Sat, 09 Sep 2017 00:21:00 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Lars Hofhansl updated PHOENIX-4165:
-----------------------------------
    Attachment: 4165-4.x-HBase-0.98.txt

4x.0.98 patch.

There seem to be subtle differences between the branches, even there is absolutely not dependencies
on the HBase version. Took quite a while to make a patch.

Very annoying, and quite easy to make mistakes this way.
How are we sure that all master patches are also in 4.x-hbase-0.98.


> Do not wait no new memory chunk can be allocated
> ------------------------------------------------
>
>                 Key: PHOENIX-4165
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4165
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.11.0
>            Reporter: Lars Hofhansl
>            Assignee: Lars Hofhansl
>             Fix For: 4.12.0
>
>         Attachments: 4165-4.x-HBase-0.98.txt, 4165.txt, 4165-v2.txt, 4165-v3.txt, 4165-v4.txt,
4165-v4.txt
>
>
> Currently the code waits for up to 10s by fault for memory to become "available".
> I think it's better to fail immediately and the let the client retry rather than waiting
on an HBase handler thread.
> In a first iteration we can simply set the max wait time to 0 (or perhaps even -1) so
that we do not attempt to wait but fail immediately. All using code should already deal with
InsufficientMemoryExceptions, since they can already happen right now,
> In a second step I'd suggest to actually remove the waiting code and config option completely.
> [~jamestaylor]



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

Mime
View raw message