First time here? Check out the FAQ!

get object Document

  • retag add tags
  2. rus0808

We received a message from the MLS that you need us to contact you regarding an issue they are seeing related to high levels of queries.

Tony's avatar
asked 2018-06-18 16:18:46 -0500
edit flag offensive 0 remove flag close merge delete



It looks like the traffic is about 371 queries per minute, which is quite a lot. Our question was in relation to the idea behind the current queries. Are you trying to build a 'base' set of data to work with, like a full download? Or is the idea behind these requests permanent?

Thank you,

Sadie's avatar Sadie (2018-06-18 16:44:00 -0500) edit
add a comment see more comments

1 Answer


This is a dynamic batch query derived from all listings in our local database that do not have any history records in batches of 50 by class. I believe we picked a batch limit of 50 because some time ago there was issues with the large history resource queries larger than 50 per query.

Yesterday we did some testing and found that the server is working well with a history batch limit of 1,000 which is the same we do for Property resource.

Beginning with today's hourly jobs the history batch has been set to 1,000 per query. This will reduce the number of queries per minute during the very short run time of 2 to 4 minutes once an hour.

Please let me know if this resolves the issue.

Tony's avatar
answered 2018-06-19 07:13:57 -0500
edit flag offensive 0 remove flag delete link


Are you actually getting any history records in your pull?

bwolven's avatar bwolven (2018-06-19 11:41:49 -0500) edit


After reviewing our logs, the last time anything was imported from the history resource was 8/30/17.

Why is that?

Tony's avatar Tony (2018-06-19 11:57:34 -0500) edit

There seems to be an issue today with our RETS downloads at 10 AM all 3 batches failed, 11 am completed without errors, 12 pm all 3 batches failed, 1 pm all 3 batches completed without errors, the 2 pm 1st batch completed without error, the 2nd batch looks like it stalled, the 3rd batch has not run yet.

Tony's avatar Tony (2018-06-19 13:16:53 -0500) edit

There were a couple of RETS refreshes done around those time periods. Those usually return "Server Temporarily Disabled" error which is what I see in our RETS logs.

Also, I don't see where you are calling "Logout" on your sessions. It would help keep our session information storage more tidy if you call "Logout" when your batch is finished.

bwolven's avatar bwolven (2018-06-19 14:05:39 -0500) edit

OK, we will add Logout to all our queries

Tony's avatar Tony (2018-06-24 09:16:18 -0500) edit

Thanks Tony. It is looking much better now.

bwolven's avatar bwolven (2018-06-26 10:49:08 -0500) edit
add a comment see more comments

Your Answer

Login/Signup to Answer