Jerry, I was able to trigger a query time out while testing with sqlline. I set the phoenix.query.timeoutMs property on the phoenix client hbase-site.xml to 1 ms and was able to trigger a timeout while querying SYSTEM.CATALOG. hbase-site.xml needs to be on the client's CLASSPATH in order to get picked up or else it will use the default timeout.
When using sqlline it sets the CLASSPATH to the HBASE_CONF_PATH environment variable which default to the current directory. -Thomas On Wed, Dec 17, 2014 at 8:27 AM, Chabot, Jerry <[email protected]> wrote: > > I am running 4.2.2 which has a fix for > https://issues.apache.org/jira/browse/PHOENIX-1463. I want to verify the > query timeout is working as expected before I set to a lower number than > the default 10 minutes. But, I can’t get a query timeout to occur. Here is > what I tried. > > > > On client: > > > > 1. Pass the phoenix.queryTimeoutMs property when getting a > DataSource. I used tomcat-jdbc to manage a set of Phoenix connections. > > 2. Call setQueryTimeout(n) on the JDBC statement. But, this returns > a SQLFeatureNotSupportedException. > > > > So I thought maybe it is only a server-side setting. I added the entry > below to the hbase-site.xml in the hbase/conf directory. I set it very > small and get reducing (now 10ms) to see if the timeout would occur. I > restarted HBase after modifying. > > > > <property> > > <name>phoenix.query.timeoutMs</name> > > <value>10</value> > > </property> > > > > I have a query that typically takes 1735m against an HBase (0.98.5) > pseudo-distributed node. But, I cannot trigger a timeout exception. > > > > Can someone clarify how the query timeout works and how I can trigger a > query timeout? > > > > -Jerry > > > > >
