Timeout adjustment SPARQL query Marklogic
I am running a simple SPARQL query which aims at counting instances of data and object properties across entities of a given class, i.e. how many organizations have been provided with a name, an address, and so on. There is only one type of entity currently loaded in the triple store so no need to filter on ?s below:
select ?attribName
from <http://example.com/graphs/orgs>
where
{
?s ?attribName ?attribValue .
}
group by
?attribName
This query times out. I can alternatively select distinct to obtain 5 or 6, but putting a higher limit will also time out after 30 seconds. There are a a few million entities.
I would like to know how to modify the timeout for SPARQL queries (not optimize the query). I've tried various timeouts in the admin console, but none seems to have an impact. This happens both when running the query from the query console or through the rest API, but nothing we change seems to have an impact on the timeout we observe.
Any idea what the right way to achieve this is? Thanks.
marklogic
edited Nov 12 at 22:45
Joel
1,5746719
asked Nov 12 at 21:57
Martin Bernier
315
add a comment |
I am running a simple SPARQL query which aims at counting instances of data and object properties across entities of a given class, i.e. how many organizations have been provided with a name, an address, and so on. There is only one type of entity currently loaded in the triple store so no need to filter on ?s below:
select ?attribName
from <http://example.com/graphs/orgs>
where
{
?s ?attribName ?attribValue .
}
group by
?attribName
This query times out. I can alternatively select distinct to obtain 5 or 6, but putting a higher limit will also time out after 30 seconds. There are a a few million entities.
I would like to know how to modify the timeout for SPARQL queries (not optimize the query). I've tried various timeouts in the admin console, but none seems to have an impact. This happens both when running the query from the query console or through the rest API, but nothing we change seems to have an impact on the timeout we observe.
Any idea what the right way to achieve this is? Thanks.
marklogic
edited Nov 12 at 22:45
Joel
1,5746719
asked Nov 12 at 21:57
Martin Bernier
315
add a comment |
I am running a simple SPARQL query which aims at counting instances of data and object properties across entities of a given class, i.e. how many organizations have been provided with a name, an address, and so on. There is only one type of entity currently loaded in the triple store so no need to filter on ?s below:
select ?attribName
from <http://example.com/graphs/orgs>
where
{
?s ?attribName ?attribValue .
}
group by
?attribName
This query times out. I can alternatively select distinct to obtain 5 or 6, but putting a higher limit will also time out after 30 seconds. There are a a few million entities.
I would like to know how to modify the timeout for SPARQL queries (not optimize the query). I've tried various timeouts in the admin console, but none seems to have an impact. This happens both when running the query from the query console or through the rest API, but nothing we change seems to have an impact on the timeout we observe.
Any idea what the right way to achieve this is? Thanks.
marklogic
edited Nov 12 at 22:45
Joel
1,5746719
asked Nov 12 at 21:57
Martin Bernier
315
I am running a simple SPARQL query which aims at counting instances of data and object properties across entities of a given class, i.e. how many organizations have been provided with a name, an address, and so on. There is only one type of entity currently loaded in the triple store so no need to filter on ?s below:
select ?attribName
from <http://example.com/graphs/orgs>
where
{
?s ?attribName ?attribValue .
}
group by
?attribName
This query times out. I can alternatively select distinct to obtain 5 or 6, but putting a higher limit will also time out after 30 seconds. There are a a few million entities.
I would like to know how to modify the timeout for SPARQL queries (not optimize the query). I've tried various timeouts in the admin console, but none seems to have an impact. This happens both when running the query from the query console or through the rest API, but nothing we change seems to have an impact on the timeout we observe.
Any idea what the right way to achieve this is? Thanks.
marklogic
marklogic
edited Nov 12 at 22:45
Joel
1,5746719
asked Nov 12 at 21:57
Martin Bernier
315
edited Nov 12 at 22:45
Joel
1,5746719
asked Nov 12 at 21:57
Martin Bernier
315
edited Nov 12 at 22:45
Joel
1,5746719
edited Nov 12 at 22:45
Joel
1,5746719
edited Nov 12 at 22:45
Joel
1,5746719
1,5746719
asked Nov 12 at 21:57
Martin Bernier
315
asked Nov 12 at 21:57
Martin Bernier
315
asked Nov 12 at 21:57
Martin Bernier
315
315
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
I don't think there is any time out for 30 seconds. You might be facing some another issue. Check this thread https://developer.marklogic.com/pipermail/general/2014-July/015483.html and you can also try something like:
import module namespace sem = "http://marklogic.com/semantics" at "/MarkLogic/semantics.xqy";
sem:sparql('select ?o
where
{
?s ?p ?o .
}
group by ?o')
which can help you to increase the MarkLogic query timeout to minimum 10 minute.
answered Nov 13 at 6:39
Navin Rawat
2,75111427
Thank you for your answer. I looked at the thread you provided as well as tried running the query through xquery, but it still stops after 30 seconds. I also played with the timeouts in the AppServer configuration, but it did not help. It does look like a 30 seconds timeout when I measure it, and it never goes over. It happens with multiple queries, as soon as they take more than 30 seconds, it stops. Through the REST I get an error 504.
– Martin Bernier
Nov 13 at 19:28
How are you executing XQuery? Through QConsole or anything else.
– Navin Rawat
Nov 14 at 9:44
Through Query Console
– Martin Bernier
Nov 14 at 14:43
Could you share the exact error which you are getting? you can share image or log.
– Navin Rawat
Nov 15 at 14:11
add a comment |
Solved. It turns out I had not set the right timeout value in the admin console. I went to the admin console, selected the app servers in the left pane. I then changed the "request timeout" field of the different app servers to a higher value. It initially did not work, but when the environment was redeployed on the next day (i.e. restart of Marklogic), the timeout became effective, and the issue was solved.
answered Nov 21 at 18:08
Martin Bernier
315
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53270697%2ftimeout-adjustment-sparql-query-marklogic%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I don't think there is any time out for 30 seconds. You might be facing some another issue. Check this thread https://developer.marklogic.com/pipermail/general/2014-July/015483.html and you can also try something like:
import module namespace sem = "http://marklogic.com/semantics" at "/MarkLogic/semantics.xqy";
sem:sparql('select ?o
where
{
?s ?p ?o .
}
group by ?o')
which can help you to increase the MarkLogic query timeout to minimum 10 minute.
answered Nov 13 at 6:39
Navin Rawat
2,75111427
Thank you for your answer. I looked at the thread you provided as well as tried running the query through xquery, but it still stops after 30 seconds. I also played with the timeouts in the AppServer configuration, but it did not help. It does look like a 30 seconds timeout when I measure it, and it never goes over. It happens with multiple queries, as soon as they take more than 30 seconds, it stops. Through the REST I get an error 504.
– Martin Bernier
Nov 13 at 19:28
How are you executing XQuery? Through QConsole or anything else.
– Navin Rawat
Nov 14 at 9:44
Through Query Console
– Martin Bernier
Nov 14 at 14:43
Could you share the exact error which you are getting? you can share image or log.
– Navin Rawat
Nov 15 at 14:11
add a comment |
I don't think there is any time out for 30 seconds. You might be facing some another issue. Check this thread https://developer.marklogic.com/pipermail/general/2014-July/015483.html and you can also try something like:
import module namespace sem = "http://marklogic.com/semantics" at "/MarkLogic/semantics.xqy";
sem:sparql('select ?o
where
{
?s ?p ?o .
}
group by ?o')
which can help you to increase the MarkLogic query timeout to minimum 10 minute.
answered Nov 13 at 6:39
Navin Rawat
2,75111427
Thank you for your answer. I looked at the thread you provided as well as tried running the query through xquery, but it still stops after 30 seconds. I also played with the timeouts in the AppServer configuration, but it did not help. It does look like a 30 seconds timeout when I measure it, and it never goes over. It happens with multiple queries, as soon as they take more than 30 seconds, it stops. Through the REST I get an error 504.
– Martin Bernier
Nov 13 at 19:28
How are you executing XQuery? Through QConsole or anything else.
– Navin Rawat
Nov 14 at 9:44
Through Query Console
– Martin Bernier
Nov 14 at 14:43
Could you share the exact error which you are getting? you can share image or log.
– Navin Rawat
Nov 15 at 14:11
add a comment |
I don't think there is any time out for 30 seconds. You might be facing some another issue. Check this thread https://developer.marklogic.com/pipermail/general/2014-July/015483.html and you can also try something like:
import module namespace sem = "http://marklogic.com/semantics" at "/MarkLogic/semantics.xqy";
sem:sparql('select ?o
where
{
?s ?p ?o .
}
group by ?o')
which can help you to increase the MarkLogic query timeout to minimum 10 minute.
answered Nov 13 at 6:39
Navin Rawat
2,75111427
I don't think there is any time out for 30 seconds. You might be facing some another issue. Check this thread https://developer.marklogic.com/pipermail/general/2014-July/015483.html and you can also try something like:
import module namespace sem = "http://marklogic.com/semantics" at "/MarkLogic/semantics.xqy";
sem:sparql('select ?o
where
{
?s ?p ?o .
}
group by ?o')
which can help you to increase the MarkLogic query timeout to minimum 10 minute.
answered Nov 13 at 6:39
Navin Rawat
2,75111427
answered Nov 13 at 6:39
Navin Rawat
2,75111427
answered Nov 13 at 6:39
Navin Rawat
2,75111427
answered Nov 13 at 6:39
Navin Rawat
2,75111427
2,75111427
Thank you for your answer. I looked at the thread you provided as well as tried running the query through xquery, but it still stops after 30 seconds. I also played with the timeouts in the AppServer configuration, but it did not help. It does look like a 30 seconds timeout when I measure it, and it never goes over. It happens with multiple queries, as soon as they take more than 30 seconds, it stops. Through the REST I get an error 504.
– Martin Bernier
Nov 13 at 19:28
How are you executing XQuery? Through QConsole or anything else.
– Navin Rawat
Nov 14 at 9:44
Through Query Console
– Martin Bernier
Nov 14 at 14:43
Could you share the exact error which you are getting? you can share image or log.
– Navin Rawat
Nov 15 at 14:11
add a comment |
Thank you for your answer. I looked at the thread you provided as well as tried running the query through xquery, but it still stops after 30 seconds. I also played with the timeouts in the AppServer configuration, but it did not help. It does look like a 30 seconds timeout when I measure it, and it never goes over. It happens with multiple queries, as soon as they take more than 30 seconds, it stops. Through the REST I get an error 504.
– Martin Bernier
Nov 13 at 19:28
How are you executing XQuery? Through QConsole or anything else.
– Navin Rawat
Nov 14 at 9:44
Through Query Console
– Martin Bernier
Nov 14 at 14:43
Could you share the exact error which you are getting? you can share image or log.
– Navin Rawat
Nov 15 at 14:11
Thank you for your answer. I looked at the thread you provided as well as tried running the query through xquery, but it still stops after 30 seconds. I also played with the timeouts in the AppServer configuration, but it did not help. It does look like a 30 seconds timeout when I measure it, and it never goes over. It happens with multiple queries, as soon as they take more than 30 seconds, it stops. Through the REST I get an error 504.
– Martin Bernier
Nov 13 at 19:28
Thank you for your answer. I looked at the thread you provided as well as tried running the query through xquery, but it still stops after 30 seconds. I also played with the timeouts in the AppServer configuration, but it did not help. It does look like a 30 seconds timeout when I measure it, and it never goes over. It happens with multiple queries, as soon as they take more than 30 seconds, it stops. Through the REST I get an error 504.
– Martin Bernier
Nov 13 at 19:28
How are you executing XQuery? Through QConsole or anything else.
– Navin Rawat
Nov 14 at 9:44
How are you executing XQuery? Through QConsole or anything else.
– Navin Rawat
Nov 14 at 9:44
Through Query Console
– Martin Bernier
Nov 14 at 14:43
Through Query Console
– Martin Bernier
Nov 14 at 14:43
Could you share the exact error which you are getting? you can share image or log.
– Navin Rawat
Nov 15 at 14:11
Could you share the exact error which you are getting? you can share image or log.
– Navin Rawat
Nov 15 at 14:11
add a comment |
Solved. It turns out I had not set the right timeout value in the admin console. I went to the admin console, selected the app servers in the left pane. I then changed the "request timeout" field of the different app servers to a higher value. It initially did not work, but when the environment was redeployed on the next day (i.e. restart of Marklogic), the timeout became effective, and the issue was solved.
answered Nov 21 at 18:08
Martin Bernier
315
add a comment |
Solved. It turns out I had not set the right timeout value in the admin console. I went to the admin console, selected the app servers in the left pane. I then changed the "request timeout" field of the different app servers to a higher value. It initially did not work, but when the environment was redeployed on the next day (i.e. restart of Marklogic), the timeout became effective, and the issue was solved.
answered Nov 21 at 18:08
Martin Bernier
315
add a comment |
Solved. It turns out I had not set the right timeout value in the admin console. I went to the admin console, selected the app servers in the left pane. I then changed the "request timeout" field of the different app servers to a higher value. It initially did not work, but when the environment was redeployed on the next day (i.e. restart of Marklogic), the timeout became effective, and the issue was solved.
answered Nov 21 at 18:08
Martin Bernier
315
Solved. It turns out I had not set the right timeout value in the admin console. I went to the admin console, selected the app servers in the left pane. I then changed the "request timeout" field of the different app servers to a higher value. It initially did not work, but when the environment was redeployed on the next day (i.e. restart of Marklogic), the timeout became effective, and the issue was solved.
answered Nov 21 at 18:08
Martin Bernier
315
answered Nov 21 at 18:08
Martin Bernier
315
answered Nov 21 at 18:08
Martin Bernier
315
answered Nov 21 at 18:08
Martin Bernier
315
315
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53270697%2ftimeout-adjustment-sparql-query-marklogic%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
