New to Cassandra here. I'm wanting to exercise a Cassandra installation hosted on a storage array, starting to drive some traffic with benchmarks/sync.py, intending to try various other benchmarks scripts, settings, etc.
Long story short, I think there's a bug in benchmarks/base.py, in the parse_options() function on or around line 200 (did a git pull just now), where the line of code in question reads:
200 log.setLevel(options.log_level.upper())If I'm understanding this properly, that's calling log.setLevel() with a string rather than say logging.INFO or logging.WARNING, and so on, per:
https://docs.python.org/2/library/logging.html#levelsPython on this particular client system (RHEL 6.5) is Python 2.6.6 (r266:84292, Sep 4 2013, 07:46:00)
Thinking I'll throw together some sort of dict to map the string:
{
"CRITICAL": logging.CRITICAL,
"ERROR": logging.ERROR,
"WARNING": logging.WARNING,
"INFO": logging.INFO,
"DEBUG": logging.DEBUG
}
cheers,
:^)
djp