Github user uce commented on a diff in the pull request:

    https://github.com/apache/flink/pull/3059#discussion_r95131517
  
    --- Diff: docs/setup/config.md ---
    @@ -162,24 +162,27 @@ will be used under the directory specified by 
jobmanager.web.tmpdir.
     
     - `high-availability.zookeeper.storageDir`: Required for HA. Directory for 
storing JobManager metadata; this is persisted in the state backend and only a 
pointer to this state is stored in ZooKeeper. Exactly like the checkpoint 
directory it must be accessible from the JobManager and a local filesystem 
should only be used for local deployments. Previously this key was named 
`recovery.zookeeper.storageDir`.
     
    -- `blob.storage.directory`: Directory for storing blobs (such as user 
jar's) on the TaskManagers.
    +- `blob.storage.directory`: Directory for storing blobs (such as user 
JARs) on the TaskManagers.
     
    -- `blob.server.port`: Port definition for the blob server (serving user 
jar's) on the Taskmanagers. By default the port is set to 0, which means that 
the operating system is picking an ephemeral port. Flink also accepts a list of 
ports ("50100,50101"), ranges ("50100-50200") or a combination of both. It is 
recommended to set a range of ports to avoid collisions when multiple 
JobManagers are running on the same machine.
    +- `blob.server.port`: Port definition for the blob server (serving user 
JARs) on the TaskManagers. By default the port is set to 0, which means that 
the operating system is picking an ephemeral port. Flink also accepts a list of 
ports ("50100,50101"), ranges ("50100-50200") or a combination of both. It is 
recommended to set a range of ports to avoid collisions when multiple 
JobManagers are running on the same machine.
     
     - `blob.service.ssl.enabled`: Flag to enable ssl for the blob 
client/server communication. This is applicable only when the global ssl flag 
security.ssl.enabled is set to true (DEFAULT: true).
     
    -- `restart-strategy`: Default restart strategy to use in case that no 
restart strategy has been specified for the submitted job.
    -Currently, it can be chosen from fixed delay restart strategy, failure 
rate restart strategy or no restart strategy.
    -To use the fixed delay strategy you have to specify "fixed-delay".
    -To use the failure rate strategy you have to specify "failure-rate".
    -To turn the restart behaviour off you have to specify "none".
    -Default value "none".
    +- `restart-strategy`: Default [restart 
strategy]({{site.baseurl}}/dev/restart_strategies.html) to use in case no 
    +restart strategy has been specified for the job.
    +The options are:
    +    - fixed delay strategy: "fixed-delay".
    --- End diff --
    
    Should we use code formatting with backticks instead of " for these as well?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to