I hereby claim:
- I am aarcro on github.
- I am luckidog (https://keybase.io/luckidog) on keybase.
- I have a public key whose fingerprint is 8AA4 D727 7E6E 7531 284F 2D06 3F8F F46F D8F2 70B3
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
@0 | |
@1 | |
LOOP: | |
MOV UP ACC | |
MOV ACC RIGHT | |
MOV ACC DOWN | |
@2 |
@0 | |
## FASTER | |
@1 | |
MOV RIGHT, DOWN | |
MOV UP, ACC | |
MOV ACC, RIGHT | |
MOV ACC, DOWN | |
@2 |
#B-14918 [solr] Logging and/or metrics around searcher warming times
Since overlapping searcher is a know issue causing cluster instability, we should start logging how long cache warming is taking. Ideally there's a logging config that can enable this, less ideally a script that loads polls for stats and loads into graphite.
Actually... I just found this in New Relic. But it's only Averaged (over time) and Agrregated (Over all the hosts), I'm not terribly certain it will help pin point bad behavior, but is good for an overall view. Transaction traces do show some outliers.
============== #B-15039 [Spike] Determine how to log Solr Queries to analyze run-away queries
We are not able to analyze the querie
try: | |
something.dangerous() | |
except Exception as e: | |
type_, value, tb = sys.exc_info() | |
traceback.print_exc() | |
pdb.post_mortem(tb) |