Indicate restart required for additional props

Update the generated server-properties.md to indicate that some
additional properties require restart to take effect. The generated
documentation for these were fixed after 2.1.3 was released, so this
change is to update the docs from the 2.1.4-SNAPSHOT build after
apache/accumulo#4780 was merged.

This fixes #438

_docs-2/configuration/server-properties.md

@@ -321,8 +321,8 @@ Below are properties set in `accumulo.properties` or the Accumulo shell that con
 | <a name="tserver_server_threadcheck_time" class="prop"></a> tserver.server.threadcheck.time | **Available since:** 1.4.0<br>The time between adjustments of the server thread pool.<br>**type:** TIMEDURATION, **zk mutable:** yes, **default value:** `1s` |
 | <a name="tserver_server_threads_minimum" class="prop"></a> tserver.server.threads.minimum | **Available since:** 1.4.0<br>The minimum number of threads to use to handle incoming requests.<br>**type:** COUNT, **zk mutable:** yes but requires restart of the tserver, **default value:** `20` |
 | <a name="tserver_server_threads_timeout" class="prop"></a> tserver.server.threads.timeout | **Available since:** 2.1.0<br>The time after which incoming request threads terminate with no work available.  Zero (0) will keep the threads alive indefinitely.<br>**type:** TIMEDURATION, **zk mutable:** yes but requires restart of the tserver, **default value:** `0s` |
-| <a name="tserver_session_idle_max" class="prop"></a> tserver.session.idle.max | **Available since:** 1.3.5<br>When a tablet server's SimpleTimer thread triggers to check idle sessions, this configurable option will be used to evaluate scan sessions to determine if they can be closed due to inactivity.<br>**type:** TIMEDURATION, **zk mutable:** yes, **default value:** `1m` |
-| <a name="tserver_session_update_idle_max" class="prop"></a> tserver.session.update.idle.max | **Available since:** 1.6.5<br>When a tablet server's SimpleTimer thread triggers to check idle sessions, this configurable option will be used to evaluate update sessions to determine if they can be closed due to inactivity.<br>**type:** TIMEDURATION, **zk mutable:** yes, **default value:** `1m` |
+| <a name="tserver_session_idle_max" class="prop"></a> tserver.session.idle.max | **Available since:** 1.3.5<br>When a tablet server's SimpleTimer thread triggers to check idle sessions, this configurable option will be used to evaluate scan sessions to determine if they can be closed due to inactivity.<br>**type:** TIMEDURATION, **zk mutable:** yes but requires restart of the tserver, **default value:** `1m` |
+| <a name="tserver_session_update_idle_max" class="prop"></a> tserver.session.update.idle.max | **Available since:** 1.6.5<br>When a tablet server's SimpleTimer thread triggers to check idle sessions, this configurable option will be used to evaluate update sessions to determine if they can be closed due to inactivity.<br>**type:** TIMEDURATION, **zk mutable:** yes but requires restart of the tserver, **default value:** `1m` |
 | <a name="tserver_slow_filepermit_time" class="prop"></a> tserver.slow.filepermit.time | **Available since:** 1.9.3<br>If a thread blocks more than this period of time waiting to get file permits, debugging information will be written.<br>**type:** TIMEDURATION, **zk mutable:** yes, **default value:** `100ms` |
 | <a name="tserver_slow_flush_time" class="prop"></a> tserver.slow.flush.time | **Available since:** 1.8.0<br>If a flush to the write-ahead log takes longer than this period of time, debugging information will written, and may result in a log rollover.<br>**type:** TIMEDURATION, **zk mutable:** yes, **default value:** `100ms` |
 | ~~<a name="tserver_sort_buffer_size" class="prop"></a> tserver.sort.buffer.size~~ | **Available since:** 1.5.0<br>*Deprecated since:* 2.1.0<br>*Replaced by:* <a href="#tserver_wal_sort_buffer_size">tserver.wal.sort.buffer.size</a><br>~~The amount of memory to use when sorting logs during recovery.~~<br>~~**type:** MEMORY~~, ~~**zk mutable:** yes~~, ~~**default value:** `10%`~~ |