Hi Pranavan, Have you tried limiting tracing to particular queries by trace on/off queries. This gives the trace id of particular queries only so that you can query tracing table matching the trace id. You can refer[1 <https://issues.apache.org/jira/browse/PHOENIX-1115?focusedCommentId=14336460&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14336460>] for more information.
1) https://issues.apache.org/jira/browse/PHOENIX-1115?focusedCommentId=14336460&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14336460 On Sun, May 15, 2016 at 3:12 PM, Pranavan Theivendiram < [email protected]> wrote: > Hi Devs! > > I am working on jira issue - > https://issues.apache.org/jira/browse/PHOENIX-2179 . I I ran SELECT * > FROM SYSTEM.TRACING_STATS. It took around 3 minutes and 20 seconds to > finish. This looks cumbersome. > > I have come up with following alternatives. > > 1. Limiting the trace output to the latest 10000 rows. > 2. Add a parameter in query to limit the number of rows > > Can someone suggests which is the best one? If you have any ideas, help me > on this issue. > > Thanks > > *T. Pranavan* > *Junior Consultant | Department of Computer Science & Engineering > ,University of Moratuwa* > *Mobile| *0775136836 >
