Google Burps a Very Interesting Error Message

• Posted by B Jones on July 5th, 2006 - Comment on this Post »

One sure way to get information about a server is to wait for it to spit up an unexpected error. It seems that someone over at DigitalPoint forums was searching Google cache when the data below was returned in an error. Something like this was surely never meant to be seen by user eyes, but as we can see here, even Google’s servers are not bullet proof.

pacemaker-alarm-delay-in-ms-overall-sum 2341989
pacemaker-alarm-delay-in-ms-total-count 7776761
cpu-utilization 1.28
cpu-speed 2800000000

timedout-queries_total 14227
num-docinfo_total 10680907
avg-latency-ms_total 3545152552
num-docinfo_total 10680907
num-docinfo-disk_total 2200918

queries_total 1229799558
e_supplemental=150000 –pagerank_cutoff_decrease_per_round=100 –pagerank_cutoff_increase_per_round=500 –parents=12,13,14,15,16,17,18,19,20,21,22,23 –pass_country_to_leaves –phil_max_doc_activation=0.5 –port_base=32311 –production –rewrite_noncompositional_compounds –rpc_resolve_unreachable_servers –scale_prvec4_to_prvec –sections_to_retrieve=body+url+compactanchors –servlets=ascorer –supplemental_tier_section=body+url+compactanchors –threaded_logging –nouse_compressed_urls –use_domain_match –nouse_experimental_indyrank –use_experimental_spamscore –use_gwd –use_query_classifier –use_spamscore –using_borg

So what does this mean? Your guess is as good as mine. Any guesses?

Heard it from the Refugee who heard it from DP

If you enjoyed this post, make sure you subscribe to my RSS feed!