Hi Chris,
another question pops up, is cursorMark cloud aware?
And if so, who is handling the cursorMark and what if a shard goes down
and comes up again?
Regards
Bernd
Am 30.06.2015 um 08:43 schrieb Bernd Fehling:
Thanks for your explanation.
Right out of your head, are there any other
Thanks for your explanation.
Right out of your head, are there any other options which prevent
getting a cursorMark?
Yes, that was also my idea to set up a separate request handler
for harvesting without timeAllowed.
As Shawn suggested, a short note about this should go into the documentation.
Hi list,
while just trying cursorMark I got the following search response:
error: {
msg: Can not search using both cursorMark and timeAllowed,
code: 400
}
Yes, I'm using timeAllowed which is set in my requestHandler as
invariant to 6 (60 seconds) as a limit to killer searches.
On 6/29/2015 9:12 AM, Bernd Fehling wrote:
while just trying cursorMark I got the following search response:
error: {
msg: Can not search using both cursorMark and timeAllowed,
code: 400
}
Yes, I'm using timeAllowed which is set in my requestHandler as
invariant to 6 (60
: Have nothing found in the ref guides, docs, wiki, examples about this
mutually
: exclusive parameters.
:
: Is this a bug or a feature and if it is a feature, where is the sense of
this?
The problem is that if a timeAllowed exceeded situation pops up, you won't
get a nextCursorMark to
