Sorry Sasi, missed your last mails.
It seems that you have one region in a table or the query touching one
region because of monotonically increasing key['MK00100','YOU',4] .
Varying performance is because you may have filter which are aggressive and
skipping lots of rows in between (*0* (7965
Any one has suggestions for the performance issue discussed in this
thread?. Your suggestions would help me resolve this issue.
Infrastructure details:
Azure HDInsight HBase
Type Node SizeCores Nodes
Head D3 V2 8 2
Region D3 V2 16 4
ZooKeeper D3 V2 12 3
Thanks,
Sasikumar
Also its not only the first time it takes time when we call
ResultSet.next().
When we iterate over ResultSet, it takes a long time initially and then
iterates faster. Again after few iterations, it takes sometime and this
goes on.
Sample observation:
Total Rows available on ResultSet : 5130
Hi Ankit,
Where does the server processing happens, on the HBase cluster
or the server where Phoenix core runs.
PFB the details you have asked for,
Query:
SELECT col1, col2, col5, col7, col11, col12 FROM SPL_FINAL where
col1='MK00100' and col2='YOU' and col3=4 and col5 in (?,?,?,?,?)
Share some more details about the query, DDL and explain plan. In Phoenix,
there are cases where we do some server processing at the time when
rs.next() is called first time but subsequent next() should be faster.
On Thu, Sep 22, 2016 at 9:52 AM, Sasikumar Natarajan
wrote:
>
Hi,
I'm using Apache Phoenix core 4.4.0-HBase-1.1 library to query the data
available on Phoenix server.
preparedStatement.executeQuery() seems to be taking less time. But to
enter into *while (rs.next()) {} *takes a long time. I would like to know
what is causing the delay to make the