Uploaded image for project: 'Blazegraph (by SYSTAP)'
  1. Blazegraph (by SYSTAP)
  2. BLZG-891

weird indefinite logTimeout-s on simple SPARQL PATH quries

    Details

    • Type: Bug
    • Status: Closed - Won't Fix
    • Resolution: Incomplete
    • Affects Version/s: BIGDATA_RELEASE_1_3_0
    • Fix Version/s: None
    • Component/s: Bigdata SAIL
    • Labels:
      None

      Description

      Whenever I do a simple ASK query with SPARQL PATH like:
      """
      PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
      PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>

      ASK WHERE {<http://my.resource.org/someResource> a / rdfs:subClassOf * <http://my.resource.org/someClass> }
      """

      It works fine and returns TRUE if <http://my.resource.org/someClass> exists and is connected to someResource with type/subclass relationships. But if there is no connection between someResource and someClass I get indefinite
      "WARN : 113685 main com.bigdata.service.AbstractTransactionService.logTimeout(AbstractTransactionService.java:482): Waiting"

      instead of FALSE. There is no justification for such timeouts as I have less than a hundred triplets in my test database

        Activity

        Hide
        bryanthompson bryanthompson added a comment -

        The line of code that is complaining is:

            /**
             * Logs periodic messages during shutdown.
             * 
             * @param elapsed
             *            The elapsed time since shutdown was requested.
             * @param unit
             *            The unit in which that time is measured.
             */
            private void logTimeout(final long elapsed, final TimeUnit unit) {
                
                log.warn("Waiting on task(s)" + ": elapsed="
                        + TimeUnit.NANOSECONDS.toMillis(elapsed) + "ms, #active="
                        + getActiveCount() + ", #readWrite="
                        + getReadWriteActiveCount() + ", #readOnly="
                        + getReadOnlyActiveCount());
        
            }
        
        

        Probably the database is failing to shutdown, perhaps because the query is not terminating.

        Please produce a junit test and attach it to this ticket. Please use the simplest example which demonstrates the problem.

        Show
        bryanthompson bryanthompson added a comment - The line of code that is complaining is: /** * Logs periodic messages during shutdown. * * @param elapsed * The elapsed time since shutdown was requested. * @param unit * The unit in which that time is measured. */ private void logTimeout(final long elapsed, final TimeUnit unit) { log.warn("Waiting on task(s)" + ": elapsed=" + TimeUnit.NANOSECONDS.toMillis(elapsed) + "ms, #active=" + getActiveCount() + ", #readWrite=" + getReadWriteActiveCount() + ", #readOnly=" + getReadOnlyActiveCount()); } Probably the database is failing to shutdown, perhaps because the query is not terminating. Please produce a junit test and attach it to this ticket. Please use the simplest example which demonstrates the problem.
        Hide
        antonkulaga antonkulaga added a comment -

        >Probably the database is failing to shutdown, perhaps because the query is not terminating.

        Thanks for clarification, although the problem was not in not understanding the timeout message but from its occurring on very common and simple query on very small dataset

        >Please produce a junit test and attach it to this ticket. Please use the simplest example which demonstrates the problem.

        I will probably do it this weekend as I switched to some other features and extracting the code into separate small repo will take some time. Meanwhile could you tell me how to configure the timeouts for quires?

        Show
        antonkulaga antonkulaga added a comment - >Probably the database is failing to shutdown, perhaps because the query is not terminating. Thanks for clarification, although the problem was not in not understanding the timeout message but from its occurring on very common and simple query on very small dataset >Please produce a junit test and attach it to this ticket. Please use the simplest example which demonstrates the problem. I will probably do it this weekend as I switched to some other features and extracting the code into separate small repo will take some time. Meanwhile could you tell me how to configure the timeouts for quires?
        Hide
        bryanthompson bryanthompson added a comment -

        Closed due to the lack of a test case.

        Show
        bryanthompson bryanthompson added a comment - Closed due to the lack of a test case.

          People

          • Assignee:
            mikepersonick mikepersonick
            Reporter:
            antonkulaga antonkulaga
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: