Fix RIAK-2702 by restricting atom usage to 1000

[bsparrow435]

riak-admin top uses $$ to randomize the name used to connect to the local Riak node. The large range of possible OS pids can result in atom table exhaustion on long running nodes/clusters. Use $RANDOM and restrict the range to 1-1000.

[thumbot]

bjs/bugfix/restrict_atom_usage ee43c4c	:arrow_right:	2.0 e41753a	:white_check_mark: completed

Looks good! :+1:

:white_check_mark: MERGE

> Started at: 2017-01-09 12:16 > Duration: 0 seconds. > Result: OK > Message: Merge Success: bjs/bugfix/restrict_atom_usage ee43c4c47d82c78b1c5e6ce6808266a6043bfc38 onto target branch: 2.0 e41753a259c62853bd2bd5a0e615c9805679a88e > Exit Code: OK > :page_facing_up:

``` Updating e41753a..ee43c4c Fast-forward (no commit created; -m option ignored) rel/files/riak-admin | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ``` --------------------------------------------------

[bsparrow435]

@JeetKunDoug

[thumbot]

bjs/bugfix/restrict_atom_usage 88177ea	:arrow_right:	2.0 e41753a	:white_check_mark: completed

Looks good! :+1:

:white_check_mark: MERGE

> Started at: 2017-01-09 12:41 > Duration: 0 seconds. > Result: OK > Message: Merge Success: bjs/bugfix/restrict_atom_usage 88177eab457bb80d76e9595e961e25b1b2cb35c8 onto target branch: 2.0 e41753a259c62853bd2bd5a0e615c9805679a88e > Exit Code: OK > :page_facing_up:

``` Updating e41753a..88177ea Fast-forward (no commit created; -m option ignored) rel/files/riak-admin | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) ``` --------------------------------------------------

[JeetKunDoug]

+1

[hazen]

+1

[JeetKunDoug]

+1