Disable setting available processors in tests
Disable setting available processors in tests

Within the same JVM, setting the number of processors available to Netty
can only be done once. However, tests randomize the number of processors
and so without intervention would attempt to set this value multiple
times. Therefore, we need to use a flag that prevents setting this value
in tests.

Relates elastic/x-pack-elasticsearch#1266

Original commit: elastic/x-pack-elasticsearch@d1271497257050a02c8ff306b85a6cf73d495af5

nknize/elasticsearch,gingerwizard/elasticsearch,HonzaKral/elasticsearch,nknize/elasticsearch,uschindler/elasticsearch,vroyer/elassandra,coding0011/elasticsearch,nknize/elasticsearch,robin13/elasticsearch,HonzaKral/elasticsearch,scorpionvicky/elasticsearch,vroyer/elassandra,strapdata/elassandra,gingerwizard/elasticsearch,strapdata/elassandra,gfyoung/elasticsearch,gingerwizard/elasticsearch,strapdata/elassandra,strapdata/elassandra,scorpionvicky/elasticsearch,gingerwizard/elasticsearch,uschindler/elasticsearch,GlenRSmith/elasticsearch,HonzaKral/elasticsearch,robin13/elasticsearch,scorpionvicky/elasticsearch,gingerwizard/elasticsearch,strapdata/elassandra,coding0011/elasticsearch,robin13/elasticsearch,uschindler/elasticsearch,coding0011/elasticsearch,scorpionvicky/elasticsearch,gfyoung/elasticsearch,GlenRSmith/elasticsearch,nknize/elasticsearch,vroyer/elassandra,GlenRSmith/elasticsearch,coding0011/elasticsearch,gfyoung/elasticsearch,uschindler/elasticsearch,scorpionvicky/elasticsearch,GlenRSmith/elasticsearch,gfyoung/elasticsearch,nknize/elasticsearch,gfyoung/elasticsearch,uschindler/elasticsearch,gingerwizard/elasticsearch,gingerwizard/elasticsearch,robin13/elasticsearch,coding0011/elasticsearch,HonzaKral/elasticsearch,GlenRSmith/elasticsearch,robin13/elasticsearch