Hitachi Vantara Pentaho Community Forums
Results 1 to 3 of 3

Thread: Query runs for couple of hours regardless of timeout set to 300

  1. #1
    Join Date
    Jun 2015
    Posts
    2

    Default Query runs for couple of hours regardless of timeout set to 300

    Hi,

    I am using pentaho 5.0 CE with saiku plugin. This is how mondrian.properties look like:

    # Allow the use of aggregates
    mondrian.rolap.aggregates.Use=true
    mondrian.rolap.aggregates.Read=true

    # mondrian.properties
    mondrian.result.limit=5000000

    ######################################################################
    # Integer property indicating timeout value, in seconds, for queries.
    # Default of 0 indicates no timeout
    mondrian.rolap.queryTimeout=300

    # Property which controls the amount of tracing displayed. Seperate from log4j.
    mondrian.trace.level=0

    # Maximum number of simultaneous queries the system will allow.
    mondrian.query.limit=40

    # Property which determines when a dimension is considered "large".
    mondrian.rolap.LargeDimensionThreshold=100

    # Boolean property that controls whether a RolapStar's aggregate data cache is cleared after each query.
    mondrian.rolap.star.disableCaching=false

    # Boolean property which controls SQL pretty-print mode.
    mondrian.rolap.generate.formatted.sql=false

    # Boolean property which controls whether the MDX parser resolves uses case-sensitive matching when looking up identifiers.
    mondrian.olap.case.sensitive=true

    # Boolean property which controls whether to use a cache for frequently evaluated expressions.
    mondrian.expCache.enable=true

    # if enabled some NON EMPTY CrossJoin will be computed in SQL
    mondrian.native.crossjoin.enable=true

    # if enabled some TopCount will be computed in SQL
    mondrian.native.topcount.enable=true

    # if enabled some Filter() will be computed in SQL
    mondrian.native.filter.enable=true

    # some NON EMPTY set operations like member.children, level.members and member descendants will be computed in SQL
    mondrian.native.nonempty.enable=true

    # enable grouping sets, if the dialect supports it.
    mondrian.rolap.groupingsets.enable=true

    # Max number of constraints in a single `IN' SQL clause.
    mondrian.rolap.maxConstraints=10000

    # Property which defines the maximum number of passes allowable while evaluating an MDX expression.
    mondrian.rolap.evaluate.MaxEvalDepth=10


    Regardless of mondrian.rolap.queryTimeout property set correctly, few queries run for a long time. Some of them DO get time out if I re-try.

    How can I debug this issue further.

    Thanks,

  2. #2
    Join Date
    Aug 2006
    Posts
    287

    Default

    You may consider upgrading to 5.3 or 5.4 (when released) this was a known issue as documented in http://jira.pentaho.com/browse/MONDRIAN-2161

  3. #3
    Join Date
    Jun 2015
    Posts
    2

    Default

    Thank you for the response.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Privacy Policy | Legal Notices | Safe Harbor Privacy Policy

Copyright © 2005 - 2019 Hitachi Vantara Corporation. All Rights Reserved.