[ https://issues.apache.org/jira/browse/PHOENIX-1463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eli Levine updated PHOENIX-1463: -------------------------------- Fix Version/s: 4.3 5.0.0 > phoenix.query.timeoutMs doesn't work as expected > ------------------------------------------------ > > Key: PHOENIX-1463 > URL: https://issues.apache.org/jira/browse/PHOENIX-1463 > Project: Phoenix > Issue Type: Bug > Affects Versions: 4.2 > Reporter: Jan Fernando > Assignee: Samarth Jain > Priority: Minor > Fix For: 5.0.0, 4.3 > > Attachments: PHOENIX-1463.patch > > > In doing performance testing with Phoenix I noticed that under heavy load we > saw queries taking as long as 300 secs even though we had set > phoenix.query.timeoutMs to 120 secs. It looks like the timeout is applied > when the parent thread waits for all the parallel scans to complete. Each > time we call rs.next() and need a to load a new chunk of data from HBase we > again run parallel scans with a new 120 sec timeout. Therefore total query > time could be timeout * # chunks scanned. I think it would be more intuitive > if the query timeout applied to the query as a whole versus resetting for > each chunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)