> On Feb. 4, 2016, 1:11 a.m., Jiang Yan Xu wrote: > > 3rdparty/libprocess/src/process.cpp, lines 2207-2208 > > <https://reviews.apache.org/r/43149/diff/2/?file=1231902#file1231902line2207> > > > > Since we do LOG(WARNING) instead of LOG(FATAL), maybe say the below so > > it's clear that we ignored the variable and moved on with the default value. > > > > `"Ignoring invalid value " << value.get() << " for > > LIBPROCESS_THREAD_COUNT";` > > Guangya Liu wrote: > What about adding more info for trouble shooting? Such as `"Ignoring > invalid value " << value.get() << " for LIBPROCESS_THREAD_COUNT, using system > defined value " << cpus;`
+1 - haosdent ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/43149/#review117725 ----------------------------------------------------------- On Feb. 4, 2016, 12:40 a.m., James Peach wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/43149/ > ----------------------------------------------------------- > > (Updated Feb. 4, 2016, 12:40 a.m.) > > > Review request for mesos, Benjamin Hindman and Jiang Yan Xu. > > > Bugs: MESOS-4592 > https://issues.apache.org/jira/browse/MESOS-4592 > > > Repository: mesos > > > Description > ------- > > Check the LIBPROCESS_THREAD_COUNT environment variable to determine > the number of threads in the libprocess thread pool. > > > Diffs > ----- > > 3rdparty/libprocess/src/process.cpp > 65a247a5bc7cf0bd6f23f6fc5c349ecce60f5ec0 > > Diff: https://reviews.apache.org/r/43149/diff/ > > > Testing > ------- > > make check on OS X. Running in production for many months. > > > Thanks, > > James Peach > >
