This is an automated email from the ASF dual-hosted git repository.

pnowojski pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/flink-web.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new cd3a0f1  Fix formating in backpressure blog v2
cd3a0f1 is described below

commit cd3a0f10017a1860290d9ce484ebb3ee75fd639c
Author: Piotr Nowojski <[email protected]>
AuthorDate: Wed Jul 7 21:50:36 2021 +0200

    Fix formating in backpressure blog v2
---
 _posts/2021-07-07-backpressure.md    |  1 +
 content/2021/07/07/backpressure.html | 11 +++++++----
 content/blog/feed.xml                | 11 +++++++----
 3 files changed, 15 insertions(+), 8 deletions(-)

diff --git a/_posts/2021-07-07-backpressure.md 
b/_posts/2021-07-07-backpressure.md
index 94977fd..ef619f9 100644
--- a/_posts/2021-07-07-backpressure.md
+++ b/_posts/2021-07-07-backpressure.md
@@ -116,6 +116,7 @@ internal buffers, will also be reported as busy.
 One limitation, however, is that `busyTimeMsPerSecond` and 
`idleTimeMsPerSecond` metrics are oblivious
 to anything that is happening in separate threads, outside of the main 
subtask’s execution loop.
 Fortunately, this is only relevant for two cases:
+
 - Custom threads that you manually spawn in your operators (a discouraged 
practice).
 - Old-style sources that implement the deprecated `SourceFunction` interface. 
Such sources will report `NaN`/`N/A`
 as the value for busyTimeMsPerSecond. For more information on the topic of 
Data Sources please
diff --git a/content/2021/07/07/backpressure.html 
b/content/2021/07/07/backpressure.html
index 9507831..f4f0b18 100644
--- a/content/2021/07/07/backpressure.html
+++ b/content/2021/07/07/backpressure.html
@@ -324,11 +324,14 @@ internal buffers, will also be reported as busy.</p>
 
 <p>One limitation, however, is that <code>busyTimeMsPerSecond</code> and 
<code>idleTimeMsPerSecond</code> metrics are oblivious
 to anything that is happening in separate threads, outside of the main 
subtask’s execution loop.
-Fortunately, this is only relevant for two cases:
-- Custom threads that you manually spawn in your operators (a discouraged 
practice).
-- Old-style sources that implement the deprecated <code>SourceFunction</code> 
interface. Such sources will report <code>NaN</code>/<code>N/A</code>
+Fortunately, this is only relevant for two cases:</p>
+
+<ul>
+  <li>Custom threads that you manually spawn in your operators (a discouraged 
practice).</li>
+  <li>Old-style sources that implement the deprecated 
<code>SourceFunction</code> interface. Such sources will report 
<code>NaN</code>/<code>N/A</code>
 as the value for busyTimeMsPerSecond. For more information on the topic of 
Data Sources please
-<a 
href="https://ci.apache.org/projects/flink/flink-docs-release-1.13/docs/dev/datastream/sources/";>take
 a look here</a>.</p>
+<a 
href="https://ci.apache.org/projects/flink/flink-docs-release-1.13/docs/dev/datastream/sources/";>take
 a look here</a>.</li>
+</ul>
 
 <div class="row front-graphic">
   <img src="/img/blog/2021-07-07-backpressure/source-task-busy.png" 
alt="Old-style sources do not report busy time" />
diff --git a/content/blog/feed.xml b/content/blog/feed.xml
index 2a709f9..9b414da 100644
--- a/content/blog/feed.xml
+++ b/content/blog/feed.xml
@@ -131,11 +131,14 @@ internal buffers, will also be reported as busy.&lt;/p&gt;
 
 &lt;p&gt;One limitation, however, is that 
&lt;code&gt;busyTimeMsPerSecond&lt;/code&gt; and 
&lt;code&gt;idleTimeMsPerSecond&lt;/code&gt; metrics are oblivious
 to anything that is happening in separate threads, outside of the main 
subtask’s execution loop.
-Fortunately, this is only relevant for two cases:
-- Custom threads that you manually spawn in your operators (a discouraged 
practice).
-- Old-style sources that implement the deprecated 
&lt;code&gt;SourceFunction&lt;/code&gt; interface. Such sources will report 
&lt;code&gt;NaN&lt;/code&gt;/&lt;code&gt;N/A&lt;/code&gt;
+Fortunately, this is only relevant for two cases:&lt;/p&gt;
+
+&lt;ul&gt;
+  &lt;li&gt;Custom threads that you manually spawn in your operators (a 
discouraged practice).&lt;/li&gt;
+  &lt;li&gt;Old-style sources that implement the deprecated 
&lt;code&gt;SourceFunction&lt;/code&gt; interface. Such sources will report 
&lt;code&gt;NaN&lt;/code&gt;/&lt;code&gt;N/A&lt;/code&gt;
 as the value for busyTimeMsPerSecond. For more information on the topic of 
Data Sources please
-&lt;a 
href=&quot;https://ci.apache.org/projects/flink/flink-docs-release-1.13/docs/dev/datastream/sources/&quot;&gt;take
 a look here&lt;/a&gt;.&lt;/p&gt;
+&lt;a 
href=&quot;https://ci.apache.org/projects/flink/flink-docs-release-1.13/docs/dev/datastream/sources/&quot;&gt;take
 a look here&lt;/a&gt;.&lt;/li&gt;
+&lt;/ul&gt;
 
 &lt;div class=&quot;row front-graphic&quot;&gt;
   &lt;img 
src=&quot;/img/blog/2021-07-07-backpressure/source-task-busy.png&quot; 
alt=&quot;Old-style sources do not report busy time&quot; /&gt;

Reply via email to