You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@phoenix.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2019/05/27 19:08:00 UTC

[jira] [Commented] (PHOENIX-5020) PhoenixMRJobSubmitter should use a long timeout when getting candidate jobs

    [ https://issues.apache.org/jira/browse/PHOENIX-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849136#comment-16849136 ] 

Lars Hofhansl commented on PHOENIX-5020:
----------------------------------------

A blocker for 6 months? Moving to 4.15.1

> PhoenixMRJobSubmitter should use a long timeout when getting candidate jobs
> ---------------------------------------------------------------------------
>
>                 Key: PHOENIX-5020
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5020
>             Project: Phoenix
>          Issue Type: Improvement
>    Affects Versions: 5.0.0, 4.14.1
>            Reporter: Geoffrey Jacoby
>            Assignee: Geoffrey Jacoby
>            Priority: Blocker
>              Labels: SFDC
>             Fix For: 4.15.0, 5.1.0
>
>
> If an environment has a huge System.Catalog (such as having many views) the query in getCandidateJobs can timeout. Because of PHOENIX-4936, this looks like there are no indexes that need an async rebuild. In addition to fixing PHOENIX-4936, we should extend the timeout. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)