1.0.3: Setting replication.max_lag_secs in YAML-config causes Replset:find_secondary to have score '0' for all nodes

[timvaillancourt]

When setting config-file the field on release 1.0.3:

production:
  ...
  replication:
    max_lag_secs: <num>
  ...

All nodes receive a score of '0' and are then chosen at random. This is incorrect as (of course) the scoring of secondaries should not be zero.

EDIT: this may be a polymorphism problem and the int is being considered to be a string. Check that the config value field becomes an int the code is able to compare.

[timvaillancourt]

Fixed in #218.