> The jdbc driver bug(kylin's server shutdown) The shutdown may likely due to Out Of Memory and crashes JVM. Tune up heap size, if you really want to return 10m rows at once.
> The cache bug This once sounds like a bug. Please open a JIRA to track. Thanks! On Thu, May 5, 2016 at 11:17 AM, [email protected] < [email protected]> wrote: > Hi all, > kylin version:1.5.0 > > 1): The jdbc driver bug(kylin's server shutdown). > I have a Cube with ten million rows. if i execute SQL > statement with kylin's jdbc driver. but whithout 'limit' (sql for example: > select * from tablename). It query all data returned. and kylin's server > shutdown. there’s a warning log as followed, which not sure be the reason: > > sizeof.ObjectGraphWalker:209 : The configured limit of 1,000 object > references was reached while attempting to calculate the size of the object > graph. > Severe performance degradation could occur if the sizing operation > continues. > This can be avoided by setting the CacheManger or Cache <sizeOfPolicy> > elements maxDepthExceededBehavior to "abort" or > adding stop points with @IgnoreSizeOf annotations. If performance > degradation is NOT an issue at the configured limit, > raise the limit value using the CacheManager or Cache <sizeOfPolicy> > elements maxDepth attribute. > > 2): The cache bug. > First: I executed sql:'select * from tablename limit 1000'; the > result : 1000 rows. > Second : I executed sql:'select * from tablename limit 4000'; > the result : 1001 rows. > why ??? > > > > > >
