Apology: Weekend Pocket Query Issues
#1
Posted 08 March 2010 - 09:35 AM
In an attempt to speed up the Pocket Query Generator, the application(s) that processes tens of thousands of Pocket Queries a day, there was a cascading number of issues that resulted in duplicate Pocket Queries going out, Pocket Queries without logs and Pocket Queries not being sent out for a certain amount of time. Also in the process, Pocket Queries were brought down to a trickle, resulting in Pocket Queries not going out at all.
We're taking this issue very seriously at Groundspeak, and we'll be focusing on increasing the capabilities over this next weekend to ensure this never, ever happens again. By increasing this capacity we'll also be prepared to offer Pocket Queries with 1,000 results instead of 500. This will happen by the anniversary of geocaching (May 2, 2010). As those veterans to geocaching know, I'm not usually one to offer dates, but this one is solid.
Again, I offer my apology for this weekend's issues.
#3
Posted 08 March 2010 - 09:41 AM
This post has been edited by CoffeeFamily5: 08 March 2010 - 09:42 AM
#4
Posted 08 March 2010 - 09:43 AM
#5
Posted 08 March 2010 - 09:47 AM
If you queue'd up a My Finds query and did not receive it please contact our support staff (contact@geocaching.com) and they will reset it for you. Use the subject line "My Finds Reset" for fastest service.
I am so sorry for the inconvenience. I hope you were still able to enjoy a fun weekend of geocaching the old fashioned way. We are taking this lapse in service seriously and making every effort to prevent this happening in the future.
Edit: changed 11 hours to 11am.
This post has been edited by OpinioNate: 08 March 2010 - 10:54 AM
#6
Posted 08 March 2010 - 09:58 AM
i agree that communication is important, but sometimes in the rush of fixing a problem we get busy trying to fix it and forget...so you have my understanding there
just don't let it happen again
one suggestion i have for such cases is perhaps have something in red at the top of the page linking to the forum announcement, similar to what was during the last downtime maintenance
hopefully everyone will see it and there won't be endless threads being started
#7
Posted 08 March 2010 - 10:00 AM
#9
Posted 08 March 2010 - 10:09 AM
Chris
#10
Posted 08 March 2010 - 10:46 AM
jholly, on Mar 8 2010, 10:00 AM, said:
Yes. That was a problem. I was clear to the team today that they are more than welcome to post in the forums if they need to. There's no need to have any artificial barriers between the community and the Groundspeak Lackey Developers.
#11
Posted 08 March 2010 - 10:47 AM
The team is working around the clock on fixing this issue and also ensuring that this does not happen again in the future. Moving forward, I promise to keep the community aware of any such changes in as real time as possible.
Once again, my sincere apologies.
Nikhil Singhal
Director of Web Development
#12
Posted 08 March 2010 - 11:09 AM
#16
Posted 08 March 2010 - 11:51 AM
Jeremy apology accepted. It showed much class on your part to send it. I know so many of us rag on the ways things are done from time to time but this post of yours has earned you much respect from me.
Again - THANK YOU!
#17
Posted 08 March 2010 - 11:51 AM
Now my question: of the five queries I have scheduled for today, I received the two odd numbered queries around 8:30 this morning, but am stll waiting on the three even numbered queries. Is that particular server still processing backlog, or has something else popped up?
#18
Posted 08 March 2010 - 11:54 AM
My compliments, also, for the great communications of late, and I happily look forward to the bigger, happier PQs.
Cheers,
VP
#19
Posted 08 March 2010 - 11:58 AM
#21
Posted 08 March 2010 - 12:05 PM
MikieP, on Mar 8 2010, 01:51 PM, said:
Now my question: of the five queries I have scheduled for today, I received the two odd numbered queries around 8:30 this morning, but am stll waiting on the three even numbered queries. Is that particular server still processing backlog, or has something else popped up?
OpinioNate, on Mar 8 2010, 11:47 AM, said:
#22
Posted 08 March 2010 - 12:16 PM
#24
Posted 08 March 2010 - 12:25 PM
#25
Posted 08 March 2010 - 12:31 PM
I have watched this go from an underground hobby to the large community that it is today and that is wonderful. I have met many new friends and seen places I would not have seen otherwise as a result of geocaching.
Being able to load 500 caches (soon to be 1000!) at a time into my DeLorme PN-40 was only once a dream when cache pages were printed one at a time.
Sure there have been growing pains but that is to be expected. Nothing great started out perfect. Time and trials make products better.
Again, just a tip of my hat and a THANK YOU for Jeremy,the Team of Lackeys and Approvers. You have unknowingly made my life (as well as tons of others) more interesting and enjoyable thru your work and selfless determination...
This post has been edited by sledgehampster: 08 March 2010 - 12:33 PM
#26
Posted 08 March 2010 - 12:31 PM
Jeremy, on Mar 8 2010, 12:35 PM, said:
Since it hasn't been explicitly stated, let me ask...
5 PQs/day with a maximum possible of 1000 each?
All types of PQs will have the new 1000 maximum (and bookmark lists are enhanced to handle 1000 entries)?
#27
Posted 08 March 2010 - 12:36 PM
leejas72, on Mar 8 2010, 12:25 PM, said:
It should be C:\, just like rest of the path. And why are you sending things to C:\Windows\system32? That is a place for system files, not gpx or other user files. But this is very off topic for this discussion, open an new thread.
This post has been edited by jholly: 08 March 2010 - 12:37 PM
#28
Posted 08 March 2010 - 12:40 PM
beejay&esskay, on Mar 8 2010, 12:31 PM, said:
Jeremy, on Mar 8 2010, 12:35 PM, said:
Since it hasn't been explicitly stated, let me ask...
5 PQs/day with a maximum possible of 1000 each?
All types of PQs will have the new 1000 maximum (and bookmark lists are enhanced to handle 1000 entries)?
5 per day @ 1,000 each. I can't promise the bookmark lists will increase in size but we can talk about it (in another thread).
#29
Posted 08 March 2010 - 12:57 PM
#30
Posted 08 March 2010 - 01:24 PM
Pax42, on Mar 8 2010, 12:57 PM, said:
THANK YOU! My Delorme is a mess now....Not only can I not get PQs to load as geocaches vs. waypoints, I cannot even get caches sent individually via the plug in now. Will this be fixed at any point?
#31
Posted 08 March 2010 - 01:27 PM
g-people, on Mar 8 2010, 02:24 PM, said:
Pax42, on Mar 8 2010, 12:57 PM, said:
THANK YOU! My Delorme is a mess now....Not only can I not get PQs to load as geocaches vs. waypoints, I cannot even get caches sent individually via the plug in now. Will this be fixed at any point?
I have a Delorme also and it's all screwed up too. I hope this is fixed and things get back to normal. I keep getting an error message in GSAK but I don't know if it's the PQ's or GSAK
#33
Posted 08 March 2010 - 01:55 PM
Current status: At this point it looks like we have several hours left. This morning we were on track for 11am, and then more caches were added and the response times from the database slowed down due to site traffic. It was this slow performance that I was attempting to fix this weekend. Believe it or not, there are now some improvements as we're getting significantly less database timeouts than we were before.
Plans for the week: There are 4 main processes that need to happen to deliver your PQs. 1) Find the pending PQs for the day. 2) Determine which caches will fulfill each PQ. 3) Fetch those caches/logs/etc 4) Email them to you and post them to a website.
* It turns out #3 is where we spend most of our time, so we're going to fixing that this week. For you tech types, we'll be using a distributed cache.
* Another plan is to start the PQs to processing at 8pm PST. If we have time this week, we plan to prioritize processing by Latitude so those of you across the Pond and further will have your PQs during the day, and to allow our side of the Pond to still log their caches for the day.
We want to make sure the generator is stable this weekend, so processing by Latitude may get pushed, but it is the plan. Any thoughts on this?
* The database is accumulating a large amount of data. We're looking into how we can better tune it for better response times.
I will post again today when the main PQ load has been processed. Currently we have 12,000 remaining.
I know this got a bit techie, but I want to make sure you have a full understanding of what we're doing to make up for this weekend and ensure it doesn't happen again.
Drew Burlingame
#35
Posted 08 March 2010 - 02:18 PM
Pax42, on Mar 8 2010, 12:57 PM, said:
I'm looking at the code now and we're pulling the version directly from your profile setting, and looking at your profile, you're set for GPX 1.0. Let me know if you're still having problems.
#36
Posted 08 March 2010 - 02:33 PM
drewburlingame, on Mar 8 2010, 01:55 PM, said:
Drew Burlingame
Thank you Drew, a most excellent post. You gave me some insight on the process I was unaware of and it helps to better understand the problems you are facing. Thank you for your efforts, I look forward to enjoying the fruits of your labor.
#37
Posted 08 March 2010 - 02:44 PM
The larger PQs will be appreciated by many, I am sure.
Keep up the great work.
#38
Posted 08 March 2010 - 02:49 PM
drewburlingame, on Mar 8 2010, 04:18 PM, said:
Pax42, on Mar 8 2010, 12:57 PM, said:
I'm looking at the code now and we're pulling the version directly from your profile setting, and looking at your profile, you're set for GPX 1.0. Let me know if you're still having problems.
Thank you for looking into it. I however, have not been having the problem since I did the fix of changing my preference setting back and forth a number of times. Many other people though keep posting with this problem. The resolution was discovered by some folks on the Delorme forums but not everyone reads the forums so they don't know why Cache Register has stopped working for them. Even some Garmin users have noted they were receiving the 1.0.1 attributes even though their preference was set to 1.0. This issue was introduced in the last update and is probably affecting hundreds of people.
Edit to add: These are the steps we have been providing people to fix the problem until Groundspeak could look into it.
1- go to GC.com and click on YOUR PROFILE
2- then click on Your Account Details
3- scroll to the bottom of that page to Your Preferences
4- if it is set to 1.0.1, skip to step 10
5- click on change
6- find GPX Version Preference and change it to 1.0.1
7- click on Save Changes
8- click on change again
9- if the GPX Version Preference setting now says 1.0, go back to step 6 (yes really)
10- find GPX Version Preference and change it to 1.0
11- click on Save Changes
12- re-run the PQs that have the version problem, the new PQs should be OK
This post has been edited by Pax42: 08 March 2010 - 03:02 PM
#39
Posted 08 March 2010 - 02:59 PM
drewburlingame, on Mar 8 2010, 01:55 PM, said:
We want to make sure the generator is stable this weekend, so processing by Latitude may get pushed, but it is the plan. Any thoughts on this?
Sounds great ... except I hope you mean you're processing by longitude not latitude
A>
#41
Posted 08 March 2010 - 03:35 PM
I've always said you guys are an amazing bunch particularly in the face of adversity. Looking forward to seeing y'all during GW8.
#42
Posted 08 March 2010 - 03:52 PM
Jeremy, on Mar 8 2010, 09:35 AM, said:
In an attempt to speed up the Pocket Query Generator, the application(s) that processes tens of thousands of Pocket Queries a day, there was a cascading number of issues that resulted in duplicate Pocket Queries going out, Pocket Queries without logs and Pocket Queries not being sent out for a certain amount of time. Also in the process, Pocket Queries were brought down to a trickle, resulting in Pocket Queries not going out at all.
We're taking this issue very seriously at Groundspeak, and we'll be focusing on increasing the capabilities over this next weekend to ensure this never, ever happens again. By increasing this capacity we'll also be prepared to offer Pocket Queries with 1,000 results instead of 500. This will happen by the anniversary of geocaching (May 2, 2010). As those veterans to geocaching know, I'm not usually one to offer dates, but this one is solid.
Again, I offer my apology for this weekend's issues.
1000, Woo Hoo
Thanks Jeremy
#43
Posted 08 March 2010 - 04:05 PM
Jeremy, on Mar 8 2010, 12:35 PM, said:
In an attempt to speed up the Pocket Query Generator, the application(s) that processes tens of thousands of Pocket Queries a day, there was a cascading number of issues that resulted in duplicate Pocket Queries going out, Pocket Queries without logs and Pocket Queries not being sent out for a certain amount of time. Also in the process, Pocket Queries were brought down to a trickle, resulting in Pocket Queries not going out at all.
We're taking this issue very seriously at Groundspeak, and we'll be focusing on increasing the capabilities over this next weekend to ensure this never, ever happens again. By increasing this capacity we'll also be prepared to offer Pocket Queries with 1,000 results instead of 500. This will happen by the anniversary of geocaching (May 2, 2010). As those veterans to geocaching know, I'm not usually one to offer dates, but this one is solid.
Again, I offer my apology for this weekend's issues.
Thanks a 1000!
#44
Posted 08 March 2010 - 04:24 PM
drewburlingame, on Mar 8 2010, 04:55 PM, said:
We want to make sure the generator is stable this weekend, so processing by Latitude may get pushed, but it is the plan. Any thoughts on this?
Drew Burlingame
(As I has been noted, it's a little worrisome that the Groundspeak guys aren't clear on latitude vs longitude.
How would starting at 8pm affect the 5/day rule? I noticed on Saturday some of my Sunday scheduled PQs running early. (Maybe an early test...or unrelated.)
Because of the other problems Sunday it wasn't clear if these early running PQs were counted as Saturday or Sunday runs. If Sunday, there needs to be a clear indication of that.
#45
Posted 08 March 2010 - 04:35 PM
Aerodoq, on Mar 8 2010, 02:59 PM, said:
drewburlingame, on Mar 8 2010, 01:55 PM, said:
We want to make sure the generator is stable this weekend, so processing by Latitude may get pushed, but it is the plan. Any thoughts on this?
Sounds great ... except I hope you mean you're processing by longitude not latitude
A>
The idea is for those who wake up first to get the first PQs, so I believe by Latitude is correct, and we may also parse into longitude chunks. We plan to get the run times down to about 6 hours, which will be an interesting challenge when we move to 1000 caches per PQ.
#46
Posted 08 March 2010 - 04:38 PM
beejay&esskay, on Mar 8 2010, 04:24 PM, said:
drewburlingame, on Mar 8 2010, 04:55 PM, said:
We want to make sure the generator is stable this weekend, so processing by Latitude may get pushed, but it is the plan. Any thoughts on this?
Drew Burlingame
(As I has been noted, it's a little worrisome that the Groundspeak guys aren't clear on latitude vs longitude.
How would starting at 8pm affect the 5/day rule? I noticed on Saturday some of my Sunday scheduled PQs running early. (Maybe an early test...or unrelated.)
Because of the other problems Sunday it wasn't clear if these early running PQs were counted as Saturday or Sunday runs. If Sunday, there needs to be a clear indication of that.
What would you like the indication to look like? "This is one of your Sunday PQs" in the e-mail?
#47
Posted 08 March 2010 - 04:43 PM
drewburlingame, on Mar 8 2010, 04:35 PM, said:
Latitude is degrees N / S of equator. Doesn't really affect sunrise / sunset (well, except for the axial tilt). Time zone is usually decided by longitude (E / W of prime meridian).
drewburlingame, on Mar 8 2010, 04:38 PM, said:
How about "Pocket Query : [PQ name] scheduled for [date]" ?
Appreciate the work and the explanation, thank you.
#49
Posted 08 March 2010 - 05:01 PM
#50
Posted 08 March 2010 - 05:40 PM
drewburlingame, on Mar 8 2010, 04:35 PM, said:
Aerodoq, on Mar 8 2010, 02:59 PM, said:
drewburlingame, on Mar 8 2010, 01:55 PM, said:
We want to make sure the generator is stable this weekend, so processing by Latitude may get pushed, but it is the plan. Any thoughts on this?
Sounds great ... except I hope you mean you're processing by longitude not latitude
A>
The idea is for those who wake up first to get the first PQs, so I believe by Latitude is correct, and we may also parse into longitude chunks. We plan to get the run times down to about 6 hours, which will be an interesting challenge when we move to 1000 caches per PQ.
Oh, the sun now rises in the south?

Help
This topic is locked







