CouchDB views are getting timeout while fetching Data
I have 120k JSON records in CouchDB, where i have created 6 views under one design document. While accessing the view it gives me timeout error.
(org.lightcouch.CouchDbException: << Status: 500 (Internal Server Error) {"error":"timeout","reason":"The request could not be processed in a reasonable amount of time."} )
CouchDB is installed on Linux environment with 8 cores and 27 GB of RAM.
i have set os_process_timeout=5000000 but still getting same error. Is there any way to avoid this timeout error?
i am getting same over on Fauxton Web Console.
couchdb-2.0 fauxton
add a comment |
I have 120k JSON records in CouchDB, where i have created 6 views under one design document. While accessing the view it gives me timeout error.
(org.lightcouch.CouchDbException: << Status: 500 (Internal Server Error) {"error":"timeout","reason":"The request could not be processed in a reasonable amount of time."} )
CouchDB is installed on Linux environment with 8 cores and 27 GB of RAM.
i have set os_process_timeout=5000000 but still getting same error. Is there any way to avoid this timeout error?
i am getting same over on Fauxton Web Console.
couchdb-2.0 fauxton
add a comment |
I have 120k JSON records in CouchDB, where i have created 6 views under one design document. While accessing the view it gives me timeout error.
(org.lightcouch.CouchDbException: << Status: 500 (Internal Server Error) {"error":"timeout","reason":"The request could not be processed in a reasonable amount of time."} )
CouchDB is installed on Linux environment with 8 cores and 27 GB of RAM.
i have set os_process_timeout=5000000 but still getting same error. Is there any way to avoid this timeout error?
i am getting same over on Fauxton Web Console.
couchdb-2.0 fauxton
I have 120k JSON records in CouchDB, where i have created 6 views under one design document. While accessing the view it gives me timeout error.
(org.lightcouch.CouchDbException: << Status: 500 (Internal Server Error) {"error":"timeout","reason":"The request could not be processed in a reasonable amount of time."} )
CouchDB is installed on Linux environment with 8 cores and 27 GB of RAM.
i have set os_process_timeout=5000000 but still getting same error. Is there any way to avoid this timeout error?
i am getting same over on Fauxton Web Console.
couchdb-2.0 fauxton
couchdb-2.0 fauxton
edited Aug 1 '17 at 14:55
James Z
11.1k71935
11.1k71935
asked Aug 1 '17 at 12:18
Suresh Vasant SargarSuresh Vasant Sargar
112
112
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I have similar issue.
couchdb error running query. reason: (timeout) the request could not be processed in a reasonable amount of time
But Im running coucdb on raspberry in docker container. I have removed constraints from couchdb container in compose file.
resources:
limits:
cpus: '0.90'
memory: 500M
But this "remove" doesnt help. I have only one view and only 170 docs ( Not thousand !)
The point is couchdb builds indexes during 2-3 mins. But during this time doesnt use all resources. (only 8 % cpu and 10% ram)
So my "solution" was to make another db, where I make changes every time, and replicate second db with first once a day. So index is build only once a day, and view is available during a day.
PS: no issues running the same db on 64bit arch in container thought.
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%2f45437588%2fcouchdb-views-are-getting-timeout-while-fetching-data%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I have similar issue.
couchdb error running query. reason: (timeout) the request could not be processed in a reasonable amount of time
But Im running coucdb on raspberry in docker container. I have removed constraints from couchdb container in compose file.
resources:
limits:
cpus: '0.90'
memory: 500M
But this "remove" doesnt help. I have only one view and only 170 docs ( Not thousand !)
The point is couchdb builds indexes during 2-3 mins. But during this time doesnt use all resources. (only 8 % cpu and 10% ram)
So my "solution" was to make another db, where I make changes every time, and replicate second db with first once a day. So index is build only once a day, and view is available during a day.
PS: no issues running the same db on 64bit arch in container thought.
add a comment |
I have similar issue.
couchdb error running query. reason: (timeout) the request could not be processed in a reasonable amount of time
But Im running coucdb on raspberry in docker container. I have removed constraints from couchdb container in compose file.
resources:
limits:
cpus: '0.90'
memory: 500M
But this "remove" doesnt help. I have only one view and only 170 docs ( Not thousand !)
The point is couchdb builds indexes during 2-3 mins. But during this time doesnt use all resources. (only 8 % cpu and 10% ram)
So my "solution" was to make another db, where I make changes every time, and replicate second db with first once a day. So index is build only once a day, and view is available during a day.
PS: no issues running the same db on 64bit arch in container thought.
add a comment |
I have similar issue.
couchdb error running query. reason: (timeout) the request could not be processed in a reasonable amount of time
But Im running coucdb on raspberry in docker container. I have removed constraints from couchdb container in compose file.
resources:
limits:
cpus: '0.90'
memory: 500M
But this "remove" doesnt help. I have only one view and only 170 docs ( Not thousand !)
The point is couchdb builds indexes during 2-3 mins. But during this time doesnt use all resources. (only 8 % cpu and 10% ram)
So my "solution" was to make another db, where I make changes every time, and replicate second db with first once a day. So index is build only once a day, and view is available during a day.
PS: no issues running the same db on 64bit arch in container thought.
I have similar issue.
couchdb error running query. reason: (timeout) the request could not be processed in a reasonable amount of time
But Im running coucdb on raspberry in docker container. I have removed constraints from couchdb container in compose file.
resources:
limits:
cpus: '0.90'
memory: 500M
But this "remove" doesnt help. I have only one view and only 170 docs ( Not thousand !)
The point is couchdb builds indexes during 2-3 mins. But during this time doesnt use all resources. (only 8 % cpu and 10% ram)
So my "solution" was to make another db, where I make changes every time, and replicate second db with first once a day. So index is build only once a day, and view is available during a day.
PS: no issues running the same db on 64bit arch in container thought.
edited Nov 21 '18 at 19:28
answered Nov 21 '18 at 9:29
Taras VaskivTaras Vaskiv
415510
415510
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.
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%2f45437588%2fcouchdb-views-are-getting-timeout-while-fetching-data%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