If you have a "bad" node (i.e. one which is unable to respond properly to internal query iteration) then you will never get a complete query result. The solution is to get the issues on the node fixed. Resuming a query after receiving such an error will only complete properly if the node issues are addressed and Query is able to iterate across clips within the date range in question on the "bad" node.
I would also suggest that while this is a useful Disaster Recovery approach, customers "losing" the Content Addresses of objects that they store should also be addressed in other procedural / operational ways.
The faulty node does not really figure in the problem, in this case, since documents I am querying are not on that node.
To get around it, I displayed the FPQueryResult_GetTimestamp() time for the first document found in my query range.
Then I used that value for the starttime of the query, and I get most of my documents quite quickly since the documents were written to the device as a single batch, but I am aways missing three to six documents from the end of my range, using the query. I use an endtime of -1.
gstuartemc
2 Intern
•
417 Posts
0
March 29th, 2011 05:00
If you have a "bad" node (i.e. one which is unable to respond properly to internal query iteration) then you will never get a complete query result. The solution is to get the issues on the node fixed. Resuming a query after receiving such an error will only complete properly if the node issues are addressed and Query is able to iterate across clips within the date range in question on the "bad" node.
I would also suggest that while this is a useful Disaster Recovery approach, customers "losing" the Content Addresses of objects that they store should also be addressed in other procedural / operational ways.
cballantine
2 Posts
0
March 30th, 2011 14:00
Hi Graham,
The faulty node does not really figure in the problem, in this case, since documents I am querying are not on that node.
To get around it, I displayed the FPQueryResult_GetTimestamp() time for the first document found in my query range.
Then I used that value for the starttime of the query, and I get most of my documents quite quickly since the documents were written to the device as a single batch, but I am aways missing three to six documents from the end of my range, using the query. I use an endtime of -1.