You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by sj...@apache.org on 2020/08/19 13:51:59 UTC
[flink-web] branch asf-site updated (e417f2a -> e7a3a96)
This is an automated email from the ASF dual-hosted git repository.
sjwiesman pushed a change to branch asf-site
in repository https://gitbox.apache.org/repos/asf/flink-web.git.
from e417f2a Rebuild site
add e2f9c67 Adding Igal's blogpost on StateFun.
add 66edf70 Pointing to the docs master instead.
new e7a3a96 rebuild site
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
_posts/2020-08-18-statefun.md | 187 +++++++++++
content/2020/08/19/statefun.html | 461 ++++++++++++++++++++++++++
content/blog/feed.xml | 256 +++++++++++---
content/blog/index.html | 41 ++-
content/blog/page10/index.html | 40 ++-
content/blog/page11/index.html | 40 ++-
content/blog/page12/index.html | 40 ++-
content/blog/page13/index.html | 25 ++
content/blog/page2/index.html | 39 ++-
content/blog/page3/index.html | 36 +-
content/blog/page4/index.html | 36 +-
content/blog/page5/index.html | 36 +-
content/blog/page6/index.html | 38 ++-
content/blog/page7/index.html | 38 ++-
content/blog/page8/index.html | 38 ++-
content/blog/page9/index.html | 40 ++-
content/img/blog/2020-08-18-statefun/1.png | Bin 0 -> 33747 bytes
content/img/blog/2020-08-18-statefun/2.png | Bin 0 -> 21984 bytes
content/img/blog/2020-08-18-statefun/3_1.png | Bin 0 -> 246327 bytes
content/img/blog/2020-08-18-statefun/3_2.png | Bin 0 -> 293276 bytes
content/img/blog/2020-08-18-statefun/5.png | Bin 0 -> 266226 bytes
content/img/blog/2020-08-18-statefun/6.png | Bin 0 -> 151264 bytes
content/img/blog/2020-08-18-statefun/7.png | Bin 0 -> 15555 bytes
content/img/blog/2020-08-18-statefun/rack.png | Bin 0 -> 94874 bytes
content/index.html | 8 +-
content/zh/index.html | 8 +-
img/blog/2020-08-18-statefun/1.png | Bin 0 -> 33747 bytes
img/blog/2020-08-18-statefun/2.png | Bin 0 -> 21984 bytes
img/blog/2020-08-18-statefun/3_1.png | Bin 0 -> 246327 bytes
img/blog/2020-08-18-statefun/3_2.png | Bin 0 -> 293276 bytes
img/blog/2020-08-18-statefun/5.png | Bin 0 -> 266226 bytes
img/blog/2020-08-18-statefun/6.png | Bin 0 -> 151264 bytes
img/blog/2020-08-18-statefun/7.png | Bin 0 -> 15555 bytes
img/blog/2020-08-18-statefun/rack.png | Bin 0 -> 94874 bytes
34 files changed, 1193 insertions(+), 214 deletions(-)
create mode 100644 _posts/2020-08-18-statefun.md
create mode 100644 content/2020/08/19/statefun.html
create mode 100755 content/img/blog/2020-08-18-statefun/1.png
create mode 100755 content/img/blog/2020-08-18-statefun/2.png
create mode 100755 content/img/blog/2020-08-18-statefun/3_1.png
create mode 100755 content/img/blog/2020-08-18-statefun/3_2.png
create mode 100755 content/img/blog/2020-08-18-statefun/5.png
create mode 100755 content/img/blog/2020-08-18-statefun/6.png
create mode 100755 content/img/blog/2020-08-18-statefun/7.png
create mode 100755 content/img/blog/2020-08-18-statefun/rack.png
create mode 100755 img/blog/2020-08-18-statefun/1.png
create mode 100755 img/blog/2020-08-18-statefun/2.png
create mode 100755 img/blog/2020-08-18-statefun/3_1.png
create mode 100755 img/blog/2020-08-18-statefun/3_2.png
create mode 100755 img/blog/2020-08-18-statefun/5.png
create mode 100755 img/blog/2020-08-18-statefun/6.png
create mode 100755 img/blog/2020-08-18-statefun/7.png
create mode 100755 img/blog/2020-08-18-statefun/rack.png
[flink-web] 01/01: rebuild site
Posted by sj...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
sjwiesman pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/flink-web.git
commit e7a3a961b5dec981eee08cf2772f20114b0f1519
Author: Seth Wiesman <sj...@gmail.com>
AuthorDate: Wed Aug 19 08:51:45 2020 -0500
rebuild site
---
content/2020/08/19/statefun.html | 461 ++++++++++++++++++++++++++
content/blog/feed.xml | 256 +++++++++++---
content/blog/index.html | 41 ++-
content/blog/page10/index.html | 40 ++-
content/blog/page11/index.html | 40 ++-
content/blog/page12/index.html | 40 ++-
content/blog/page13/index.html | 25 ++
content/blog/page2/index.html | 39 ++-
content/blog/page3/index.html | 36 +-
content/blog/page4/index.html | 36 +-
content/blog/page5/index.html | 36 +-
content/blog/page6/index.html | 38 ++-
content/blog/page7/index.html | 38 ++-
content/blog/page8/index.html | 38 ++-
content/blog/page9/index.html | 40 ++-
content/img/blog/2020-08-18-statefun/1.png | Bin 0 -> 33747 bytes
content/img/blog/2020-08-18-statefun/2.png | Bin 0 -> 21984 bytes
content/img/blog/2020-08-18-statefun/3_1.png | Bin 0 -> 246327 bytes
content/img/blog/2020-08-18-statefun/3_2.png | Bin 0 -> 293276 bytes
content/img/blog/2020-08-18-statefun/5.png | Bin 0 -> 266226 bytes
content/img/blog/2020-08-18-statefun/6.png | Bin 0 -> 151264 bytes
content/img/blog/2020-08-18-statefun/7.png | Bin 0 -> 15555 bytes
content/img/blog/2020-08-18-statefun/rack.png | Bin 0 -> 94874 bytes
content/index.html | 8 +-
content/zh/index.html | 8 +-
25 files changed, 1006 insertions(+), 214 deletions(-)
diff --git a/content/2020/08/19/statefun.html b/content/2020/08/19/statefun.html
new file mode 100644
index 0000000..67ab932
--- /dev/null
+++ b/content/2020/08/19/statefun.html
@@ -0,0 +1,461 @@
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <meta charset="utf-8">
+ <meta http-equiv="X-UA-Compatible" content="IE=edge">
+ <meta name="viewport" content="width=device-width, initial-scale=1">
+ <!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
+ <title>Apache Flink: Monitoring and Controlling Networks of IoT Devices with Flink Stateful Functions</title>
+ <link rel="shortcut icon" href="/favicon.ico" type="image/x-icon">
+ <link rel="icon" href="/favicon.ico" type="image/x-icon">
+
+ <!-- Bootstrap -->
+ <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.4.1/css/bootstrap.min.css">
+ <link rel="stylesheet" href="/css/flink.css">
+ <link rel="stylesheet" href="/css/syntax.css">
+
+ <!-- Blog RSS feed -->
+ <link href="/blog/feed.xml" rel="alternate" type="application/rss+xml" title="Apache Flink Blog: RSS feed" />
+
+ <!-- jQuery (necessary for Bootstrap's JavaScript plugins) -->
+ <!-- We need to load Jquery in the header for custom google analytics event tracking-->
+ <script src="/js/jquery.min.js"></script>
+
+ <!-- HTML5 shim and Respond.js for IE8 support of HTML5 elements and media queries -->
+ <!-- WARNING: Respond.js doesn't work if you view the page via file:// -->
+ <!--[if lt IE 9]>
+ <script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>
+ <script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
+ <![endif]-->
+ </head>
+ <body>
+
+
+ <!-- Main content. -->
+ <div class="container">
+ <div class="row">
+
+
+ <div id="sidebar" class="col-sm-3">
+
+
+<!-- Top navbar. -->
+ <nav class="navbar navbar-default">
+ <!-- The logo. -->
+ <div class="navbar-header">
+ <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#bs-example-navbar-collapse-1">
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ <span class="icon-bar"></span>
+ </button>
+ <div class="navbar-logo">
+ <a href="/">
+ <img alt="Apache Flink" src="/img/flink-header-logo.svg" width="147px" height="73px">
+ </a>
+ </div>
+ </div><!-- /.navbar-header -->
+
+ <!-- The navigation links. -->
+ <div class="collapse navbar-collapse" id="bs-example-navbar-collapse-1">
+ <ul class="nav navbar-nav navbar-main">
+
+ <!-- First menu section explains visitors what Flink is -->
+
+ <!-- What is Stream Processing? -->
+ <!--
+ <li><a href="/streamprocessing1.html">What is Stream Processing?</a></li>
+ -->
+
+ <!-- What is Flink? -->
+ <li><a href="/flink-architecture.html">What is Apache Flink?</a></li>
+
+
+
+ <!-- What is Stateful Functions? -->
+
+ <li><a href="/stateful-functions.html">What is Stateful Functions?</a></li>
+
+ <!-- Use cases -->
+ <li><a href="/usecases.html">Use Cases</a></li>
+
+ <!-- Powered by -->
+ <li><a href="/poweredby.html">Powered By</a></li>
+
+
+
+ <!-- Second menu section aims to support Flink users -->
+
+ <!-- Downloads -->
+ <li><a href="/downloads.html">Downloads</a></li>
+
+ <!-- Getting Started -->
+ <li class="dropdown">
+ <a class="dropdown-toggle" data-toggle="dropdown" href="#">Getting Started<span class="caret"></span></a>
+ <ul class="dropdown-menu">
+ <li><a href="https://ci.apache.org/projects/flink/flink-docs-release-1.11/getting-started/index.html" target="_blank">With Flink <small><span class="glyphicon glyphicon-new-window"></span></small></a></li>
+ <li><a href="https://ci.apache.org/projects/flink/flink-statefun-docs-release-2.1/getting-started/project-setup.html" target="_blank">With Flink Stateful Functions <small><span class="glyphicon glyphicon-new-window"></span></small></a></li>
+ <li><a href="/training.html">Training Course</a></li>
+ </ul>
+ </li>
+
+ <!-- Documentation -->
+ <li class="dropdown">
+ <a class="dropdown-toggle" data-toggle="dropdown" href="#">Documentation<span class="caret"></span></a>
+ <ul class="dropdown-menu">
+ <li><a href="https://ci.apache.org/projects/flink/flink-docs-release-1.11" target="_blank">Flink 1.11 (Latest stable release) <small><span class="glyphicon glyphicon-new-window"></span></small></a></li>
+ <li><a href="https://ci.apache.org/projects/flink/flink-docs-master" target="_blank">Flink Master (Latest Snapshot) <small><span class="glyphicon glyphicon-new-window"></span></small></a></li>
+ <li><a href="https://ci.apache.org/projects/flink/flink-statefun-docs-release-2.1" target="_blank">Flink Stateful Functions 2.1 (Latest stable release) <small><span class="glyphicon glyphicon-new-window"></span></small></a></li>
+ <li><a href="https://ci.apache.org/projects/flink/flink-statefun-docs-master" target="_blank">Flink Stateful Functions Master (Latest Snapshot) <small><span class="glyphicon glyphicon-new-window"></span></small></a></li>
+ </ul>
+ </li>
+
+ <!-- getting help -->
+ <li><a href="/gettinghelp.html">Getting Help</a></li>
+
+ <!-- Blog -->
+ <li><a href="/blog/"><b>Flink Blog</b></a></li>
+
+
+ <!-- Flink-packages -->
+ <li>
+ <a href="https://flink-packages.org" target="_blank">flink-packages.org <small><span class="glyphicon glyphicon-new-window"></span></small></a>
+ </li>
+
+
+ <!-- Third menu section aim to support community and contributors -->
+
+ <!-- Community -->
+ <li><a href="/community.html">Community & Project Info</a></li>
+
+ <!-- Roadmap -->
+ <li><a href="/roadmap.html">Roadmap</a></li>
+
+ <!-- Contribute -->
+ <li><a href="/contributing/how-to-contribute.html">How to Contribute</a></li>
+
+
+ <!-- GitHub -->
+ <li>
+ <a href="https://github.com/apache/flink" target="_blank">Flink on GitHub <small><span class="glyphicon glyphicon-new-window"></span></small></a>
+ </li>
+
+
+
+ <!-- Language Switcher -->
+ <li>
+
+
+ <a href="/zh/2020/08/19/statefun.html">中文版</a>
+
+
+ </li>
+
+ </ul>
+
+ <ul class="nav navbar-nav navbar-bottom">
+ <hr />
+
+ <!-- Twitter -->
+ <li><a href="https://twitter.com/apacheflink" target="_blank">@ApacheFlink <small><span class="glyphicon glyphicon-new-window"></span></small></a></li>
+
+ <!-- Visualizer -->
+ <li class=" hidden-md hidden-sm"><a href="/visualizer/" target="_blank">Plan Visualizer <small><span class="glyphicon glyphicon-new-window"></span></small></a></li>
+
+ <hr />
+
+ <li><a href="https://apache.org" target="_blank">Apache Software Foundation <small><span class="glyphicon glyphicon-new-window"></span></small></a></li>
+
+ <li>
+ <style>
+ .smalllinks:link {
+ display: inline-block !important; background: none; padding-top: 0px; padding-bottom: 0px; padding-right: 0px; min-width: 75px;
+ }
+ </style>
+
+ <a class="smalllinks" href="https://www.apache.org/licenses/" target="_blank">License</a> <small><span class="glyphicon glyphicon-new-window"></span></small>
+
+ <a class="smalllinks" href="https://www.apache.org/security/" target="_blank">Security</a> <small><span class="glyphicon glyphicon-new-window"></span></small>
+
+ <a class="smalllinks" href="https://www.apache.org/foundation/sponsorship.html" target="_blank">Donate</a> <small><span class="glyphicon glyphicon-new-window"></span></small>
+
+ <a class="smalllinks" href="https://www.apache.org/foundation/thanks.html" target="_blank">Thanks</a> <small><span class="glyphicon glyphicon-new-window"></span></small>
+ </li>
+
+ </ul>
+ </div><!-- /.navbar-collapse -->
+ </nav>
+
+ </div>
+ <div class="col-sm-9">
+ <div class="row-fluid">
+ <div class="col-sm-12">
+ <div class="row">
+ <h1>Monitoring and Controlling Networks of IoT Devices with Flink Stateful Functions</h1>
+ <p><i></i></p>
+
+ <article>
+ <p>19 Aug 2020 Igal Shilman (<a href="https://twitter.com/IgalShilman">@IgalShilman</a>)</p>
+
+<p>In this blog post, we’ll take a look at a class of use cases that is a natural fit for <a href="https://flink.apache.org/stateful-functions.html">Flink Stateful Functions</a>: monitoring and controlling networks of connected devices (often called the “Internet of Things” (IoT)).</p>
+
+<p>IoT networks are composed of many individual, but interconnected components, which makes getting some kind of high-level insight into the status, problems, or optimization opportunities in these networks not trivial. Each individual device “sees” only its own state, which means that the status of groups of devices, or even the network as a whole, is often a complex aggregation of the individual devices’ state. Diagnosing, controlling, or optimizing these groups of devices thus require [...]
+
+<p>A powerful approach to implement this is using <em><a href="https://en.wikipedia.org/wiki/Digital_twin">digital twins</a></em>: each device has a corresponding virtual entity (i.e. the digital twin), which also captures their relationships and interactions. The digital twins track the status of their corresponding devices and send updates to other twins, representing groups (such as geographical regions) of devices. Those, in turn, handle the logic to obtain the network’s aggregated v [...]
+
+<h1 id="our-scenario-datacenter-monitoring-and-alerting">Our Scenario: Datacenter Monitoring and Alerting</h1>
+
+<figure style="float:right;padding-left:1px;padding-top: 20px">
+ <img src="/img/blog/2020-08-18-statefun/rack.png" width="350px" />
+ <figcaption style="padding-top: 10px;text-align:center"><b>Fig.1</b> An oversimplified view of a data center.</figcaption>
+</figure>
+
+<p>There are many examples of the digital twins approach in the real world, such as <a href="https://www.infoq.com/presentations/tesla-vpp/">smart grids of batteries</a>, <a href="https://www.alibabacloud.com/solutions/intelligence-brain/city">smart cities</a>, or <a href="https://www.youtube.com/watch?v=9y27FJgz5-M">monitoring infrastructure software clusters</a>. In this blogpost, we’ll use the example of data center monitoring and alert correlation implemented with Stateful Functions.</p>
+
+<p>Consider a very simplified view of a data center, consisting of many thousands of commodity servers arranged in server racks. Each server rack typically contains up to 40 servers, with a ToR (Top of the Rack) network switch connected to each server. The switches from all the racks connect through a larger switch (<strong>Fig. 1</strong>).</p>
+
+<p>In this datacenter, many things can go wrong: a disk in a server can stop working, network cards can start dropping packets, or ToR switches might cease to function. The entire data center might also be affected by power supply degradation, causing servers to operate at reduced capacity. On-site engineers must be able to identify these incidents quickly and fix them promptly.</p>
+
+<p>Diagnosing individual server failures is rather straightforward: take a recent history of metric reports from that particular server, analyse it and pinpoint the anomaly. On the other hand, other incidents only make sense “together”, because they share a common root cause. Diagnosing or predicting causes of networking degradation at a rack or datacenter level requires an aggregate view of metrics (such as package drop rates) from the individual machines and racks, and possibly some pr [...]
+
+<h2 id="monitoring-a-virtual-datacenter-via-digital-twins">Monitoring a Virtual Datacenter via Digital Twins</h2>
+
+<p>For the sake of this blog post, our oversimplified data center has some servers and racks, each with a unique ID. Each server has a metrics-collecting daemon that publishes metrics to a message queue, and there is a provisioning service that operators will use to ask for server commission- and decommissioning.</p>
+
+<div style="line-height:60%;">
+ <br />
+</div>
+
+<center>
+<img src="/img/blog/2020-08-18-statefun/1.png" width="550px" alt="" />
+</center>
+
+<div style="line-height:60%;">
+ <br />
+</div>
+
+<p>Our application will consume these server metrics and commission/decommission events, and produce server/rack/datacenter alerts. There will also be an operator consuming any alerts triggered by the monitoring system. In the next section, we’ll show how this use case can be naturally modeled with Stateful Functions (StateFun).</p>
+
+<h2 id="implementing-the-use-case-with-flink-statefun">Implementing the use case with Flink StateFun</h2>
+
+<div class="alert alert-info">
+ <p>You can find the code for this example at: <a href="https://github.com/igalshilman/iot-statefun-blogpost">https://github.com/igalshilman/iot-statefun-blogpost</a></p>
+</div>
+
+<p>The basic building block for modeling a StateFun application is a <a href="https://ci.apache.org/projects/flink/flink-statefun-docs-release-2.1/concepts/application-building-blocks.html#stateful-functions"><em>stateful function</em></a>, which has the following properties:</p>
+
+<ul>
+ <li>
+ <p>It has a logical unique address; and persisted, fault tolerant state, scoped to that address.</p>
+ </li>
+ <li>
+ <p>It can <em>react</em> to messages, both internal (or, sent from other stateful functions) and external (e.g. a message from Kafka).</p>
+ </li>
+ <li>
+ <p>Invocations of a specific function are serializable, so messages sent to a specific address are <strong>not</strong> executed concurrently.</p>
+ </li>
+ <li>
+ <p>There can be many billions of function instances in a single StateFun cluster.</p>
+ </li>
+</ul>
+
+<p>To model our use case, we’ll define three functions: <strong>ServerFun</strong>, <strong>RackFun</strong> and <strong>DataCenterFun</strong>.</p>
+
+<p><strong>ServerFun</strong></p>
+
+<p>Each physical server is represented with its <em>digital twin</em> stateful function. This function is responsible for:</p>
+
+<ol>
+ <li>
+ <p>Maintaining a sliding window of incoming metrics.</p>
+ </li>
+ <li>
+ <p>Applying a model that decides whether or not to trigger an alert.</p>
+ </li>
+ <li>
+ <p>Alerting if metrics are missing for too long.</p>
+ </li>
+ <li>
+ <p>Notifying its containing <strong>RackFun</strong> about any open incidents.</p>
+ </li>
+</ol>
+
+<p><strong>RackFun</strong></p>
+
+<p>While the <em>ServerFun</em> is responsible for identifying server-local incidents, we need a function that correlates incidents happening on the different servers deployed in the same rack and:</p>
+
+<ol>
+ <li>
+ <p>Collects open incidents reported by the <strong>ServerFun</strong> functions.</p>
+ </li>
+ <li>
+ <p>Maintains an histogram of currently opened incidents on this rack.</p>
+ </li>
+ <li>
+ <p>Applies a correlation model to the individual incidents sent by the <strong>ServerFun</strong>, and reports high-level, related incidents as a single incident to the <strong>DataCenterFun</strong>.</p>
+ </li>
+</ol>
+
+<p><strong>DataCenterFun</strong></p>
+
+<p>This function maintains a view of incidents across different racks in our datacenter.</p>
+
+<div style="line-height:60%;">
+ <br />
+</div>
+
+<center>
+<img src="/img/blog/2020-08-18-statefun/2.png" width="600px" alt="" />
+</center>
+
+<div style="line-height:60%;">
+ <br />
+</div>
+
+<p>To summarize our plan:</p>
+
+<ul>
+ <li>
+ <p>Leaf functions ingest raw metric data (<span style="color:blue">blue</span> lines), and apply localized logic to trigger an alert.</p>
+ </li>
+ <li>
+ <p>Intermediate functions operate on already summarized events (<span style="color:orange">orange</span> lines) and correlate them into high-level events.</p>
+ </li>
+ <li>
+ <p>A root function correlates the high-level events across the intermediate functions and into a single <em>healthy/not healthy</em> value.</p>
+ </li>
+</ul>
+
+<h2 id="how-does-it-really-look">How does it really look?</h2>
+
+<h3 id="serverfun">ServerFun</h3>
+
+<center>
+<img src="/img/blog/2020-08-18-statefun/3_1.png" width="600px" alt="" />
+</center>
+
+<div style="line-height:60%;">
+ <br />
+</div>
+
+<ol>
+ <li>This section associates a behaviour for every message that the function expects to be invoked with.</li>
+ <li>The <code>metricsHistory</code> buffer is our sliding window of the last 15 minutes worth of <code>ServerMetricReports</code>. Note that this buffer is configured to expire entries 15 minutes after they were written.</li>
+ <li><code>serverHealthState</code> represents the current physical server state, open incidents and so on.</li>
+</ol>
+
+<p>Let’s take a look at what happens when a <code>ServerMetricReport</code> message arrives:</p>
+
+<center>
+<img src="/img/blog/2020-08-18-statefun/3_2.png" width="600px" alt="" />
+</center>
+
+<div style="line-height:60%;">
+ <br />
+</div>
+
+<ol>
+ <li>Retrieve the previously computed <code>serverHealthState</code> that is kept in state.</li>
+ <li>Evaluate a model on the sliding window of the previous metric reports + the current metric reported + the previously computed server state to obtain an assessment of the current server health.</li>
+ <li>If the server is not believed to be healthy, emit an alert via an alerts topic, and also send a message to our containing rack with all the open incidents that this server currently has.</li>
+</ol>
+
+<div class="alert alert-warning">
+ <p>We’ll omit the other handlers for brevity, but it’s important to mention that <b>onTimer</b> makes sure that metric reports are coming in periodically, otherwise it’d trigger an alert stating that we didn’t hear from that server for a long time.</p>
+</div>
+
+<h3 id="rackfun">RackFun</h3>
+
+<center>
+<img src="/img/blog/2020-08-18-statefun/5.png" width="650px" alt="" />
+</center>
+
+<div style="line-height:60%;">
+ <br />
+</div>
+
+<ol>
+ <li>This function keeps a mapping between a <code>ServerId</code> and a set of open incidents on that server.</li>
+ <li>When new alerts are received, this function tries to correlate the alert with any other open alerts on that rack. If a correlated rack alert is present, this function notifies the <strong>DataCenterFun</strong> about it.</li>
+</ol>
+
+<h3 id="datacenterfun">DataCenterFun</h3>
+
+<center>
+<img src="/img/blog/2020-08-18-statefun/6.png" width="650px" alt="" />
+</center>
+
+<div style="line-height:60%;">
+ <br />
+</div>
+
+<ol>
+ <li>A persisted mapping between a <code>RackId</code> and the latest alert that rack reported.</li>
+ <li>Throughout the usage of ingress/egress pairs, this function can report back its current view of the world of what racks are currently known to be unhealthy.</li>
+ <li>An operator (via a front-end) can send a <code>GetUnhealthyRacks</code> message addressed to that <strong>DataCenterFun</strong>, and wait for the corresponding response <code>message(UnhealthyRacks)</code>. Whenever a rack reports <em>OK</em>, it’ll be removed from the unhealthy racks map.</li>
+</ol>
+
+<h2 id="conclusion">Conclusion</h2>
+
+<p>This pattern — where each layer of functions performs a stateful aggregation of events sent from the previous layer (or the input) — is useful for a whole class of problems. And, although we used connected devices to motivate this use case, it’s not limited to the IoT domain.</p>
+
+<center>
+<img src="/img/blog/2020-08-18-statefun/7.png" width="500px" alt="" />
+</center>
+
+<div style="line-height:60%;">
+ <br />
+</div>
+
+<p>Stateful Functions provides the building blocks necessary for building complex distributed applications (here the digital twins that support analysis and interactions of the physical entities), while removing common complexities of distributed systems like service discovery, retires, circuit breakers, state management, scalability and similar challenges. If you’d like to learn more about Stateful Functions, head over to the official <a href="https://ci.apache.org/projects/flink/flink- [...]
+
+ </article>
+ </div>
+
+ <div class="row">
+ <div id="disqus_thread"></div>
+ <script type="text/javascript">
+ /* * * CONFIGURATION VARIABLES: EDIT BEFORE PASTING INTO YOUR WEBPAGE * * */
+ var disqus_shortname = 'stratosphere-eu'; // required: replace example with your forum shortname
+
+ /* * * DON'T EDIT BELOW THIS LINE * * */
+ (function() {
+ var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true;
+ dsq.src = '//' + disqus_shortname + '.disqus.com/embed.js';
+ (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq);
+ })();
+ </script>
+ </div>
+ </div>
+</div>
+ </div>
+ </div>
+
+ <hr />
+
+ <div class="row">
+ <div class="footer text-center col-sm-12">
+ <p>Copyright © 2014-2019 <a href="http://apache.org">The Apache Software Foundation</a>. All Rights Reserved.</p>
+ <p>Apache Flink, Flink®, Apache®, the squirrel logo, and the Apache feather logo are either registered trademarks or trademarks of The Apache Software Foundation.</p>
+ <p><a href="/privacy-policy.html">Privacy Policy</a> · <a href="/blog/feed.xml">RSS feed</a></p>
+ </div>
+ </div>
+ </div><!-- /.container -->
+
+ <!-- Include all compiled plugins (below), or include individual files as needed -->
+ <script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.4/js/bootstrap.min.js"></script>
+ <script src="https://cdnjs.cloudflare.com/ajax/libs/jquery.matchHeight/0.7.0/jquery.matchHeight-min.js"></script>
+ <script src="/js/codetabs.js"></script>
+ <script src="/js/stickysidebar.js"></script>
+
+ <!-- Google Analytics -->
+ <script>
+ (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
+ (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
+ m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
+ })(window,document,'script','//www.google-analytics.com/analytics.js','ga');
+
+ ga('create', 'UA-52545728-1', 'auto');
+ ga('send', 'pageview');
+ </script>
+ </body>
+</html>
diff --git a/content/blog/feed.xml b/content/blog/feed.xml
index 85ec175..33f3413 100644
--- a/content/blog/feed.xml
+++ b/content/blog/feed.xml
@@ -7,6 +7,225 @@
<atom:link href="https://flink.apache.org/blog/feed.xml" rel="self" type="application/rss+xml" />
<item>
+<title>Monitoring and Controlling Networks of IoT Devices with Flink Stateful Functions</title>
+<description><p>In this blog post, we’ll take a look at a class of use cases that is a natural fit for <a href="https://flink.apache.org/stateful-functions.html">Flink Stateful Functions</a>: monitoring and controlling networks of connected devices (often called the “Internet of Things” (IoT)).</p>
+
+<p>IoT networks are composed of many individual, but interconnected components, which makes getting some kind of high-level insight into the status, problems, or optimization opportunities in these networks not trivial. Each individual device “sees” only its own state, which means that the status of groups of devices, or even the network as a whole, is often a complex aggregation of the individual devices’ state. Diagnosing, controlling, or optimizing these groups of devices thus r [...]
+
+<p>A powerful approach to implement this is using <em><a href="https://en.wikipedia.org/wiki/Digital_twin">digital twins</a></em>: each device has a corresponding virtual entity (i.e. the digital twin), which also captures their relationships and interactions. The digital twins track the status of their corresponding devices and send updates to other twins, representing groups (such as geographical regions) of devices. Those, in turn, handle the lo [...]
+
+<h1 id="our-scenario-datacenter-monitoring-and-alerting">Our Scenario: Datacenter Monitoring and Alerting</h1>
+
+<figure style="float:right;padding-left:1px;padding-top: 20px">
+ <img src="/img/blog/2020-08-18-statefun/rack.png" width="350px" />
+ <figcaption style="padding-top: 10px;text-align:center"><b>Fig.1</b> An oversimplified view of a data center.</figcaption>
+</figure>
+
+<p>There are many examples of the digital twins approach in the real world, such as <a href="https://www.infoq.com/presentations/tesla-vpp/">smart grids of batteries</a>, <a href="https://www.alibabacloud.com/solutions/intelligence-brain/city">smart cities</a>, or <a href="https://www.youtube.com/watch?v=9y27FJgz5-M">monitoring infrastructure software clusters</a>. In this blogpost, we’ll use the example of data cent [...]
+
+<p>Consider a very simplified view of a data center, consisting of many thousands of commodity servers arranged in server racks. Each server rack typically contains up to 40 servers, with a ToR (Top of the Rack) network switch connected to each server. The switches from all the racks connect through a larger switch (<strong>Fig. 1</strong>).</p>
+
+<p>In this datacenter, many things can go wrong: a disk in a server can stop working, network cards can start dropping packets, or ToR switches might cease to function. The entire data center might also be affected by power supply degradation, causing servers to operate at reduced capacity. On-site engineers must be able to identify these incidents quickly and fix them promptly.</p>
+
+<p>Diagnosing individual server failures is rather straightforward: take a recent history of metric reports from that particular server, analyse it and pinpoint the anomaly. On the other hand, other incidents only make sense “together”, because they share a common root cause. Diagnosing or predicting causes of networking degradation at a rack or datacenter level requires an aggregate view of metrics (such as package drop rates) from the individual machines and racks, and possibly s [...]
+
+<h2 id="monitoring-a-virtual-datacenter-via-digital-twins">Monitoring a Virtual Datacenter via Digital Twins</h2>
+
+<p>For the sake of this blog post, our oversimplified data center has some servers and racks, each with a unique ID. Each server has a metrics-collecting daemon that publishes metrics to a message queue, and there is a provisioning service that operators will use to ask for server commission- and decommissioning.</p>
+
+<div style="line-height:60%;">
+ <br />
+</div>
+
+<center>
+<img src="/img/blog/2020-08-18-statefun/1.png" width="550px" alt="" />
+</center>
+
+<div style="line-height:60%;">
+ <br />
+</div>
+
+<p>Our application will consume these server metrics and commission/decommission events, and produce server/rack/datacenter alerts. There will also be an operator consuming any alerts triggered by the monitoring system. In the next section, we’ll show how this use case can be naturally modeled with Stateful Functions (StateFun).</p>
+
+<h2 id="implementing-the-use-case-with-flink-statefun">Implementing the use case with Flink StateFun</h2>
+
+<div class="alert alert-info">
+ <p>You can find the code for this example at: <a href="https://github.com/igalshilman/iot-statefun-blogpost">https://github.com/igalshilman/iot-statefun-blogpost</a></p>
+</div>
+
+<p>The basic building block for modeling a StateFun application is a <a href="https://ci.apache.org/projects/flink/flink-statefun-docs-release-2.1/concepts/application-building-blocks.html#stateful-functions"><em>stateful function</em></a>, which has the following properties:</p>
+
+<ul>
+ <li>
+ <p>It has a logical unique address; and persisted, fault tolerant state, scoped to that address.</p>
+ </li>
+ <li>
+ <p>It can <em>react</em> to messages, both internal (or, sent from other stateful functions) and external (e.g. a message from Kafka).</p>
+ </li>
+ <li>
+ <p>Invocations of a specific function are serializable, so messages sent to a specific address are <strong>not</strong> executed concurrently.</p>
+ </li>
+ <li>
+ <p>There can be many billions of function instances in a single StateFun cluster.</p>
+ </li>
+</ul>
+
+<p>To model our use case, we’ll define three functions: <strong>ServerFun</strong>, <strong>RackFun</strong> and <strong>DataCenterFun</strong>.</p>
+
+<p><strong>ServerFun</strong></p>
+
+<p>Each physical server is represented with its <em>digital twin</em> stateful function. This function is responsible for:</p>
+
+<ol>
+ <li>
+ <p>Maintaining a sliding window of incoming metrics.</p>
+ </li>
+ <li>
+ <p>Applying a model that decides whether or not to trigger an alert.</p>
+ </li>
+ <li>
+ <p>Alerting if metrics are missing for too long.</p>
+ </li>
+ <li>
+ <p>Notifying its containing <strong>RackFun</strong> about any open incidents.</p>
+ </li>
+</ol>
+
+<p><strong>RackFun</strong></p>
+
+<p>While the <em>ServerFun</em> is responsible for identifying server-local incidents, we need a function that correlates incidents happening on the different servers deployed in the same rack and:</p>
+
+<ol>
+ <li>
+ <p>Collects open incidents reported by the <strong>ServerFun</strong> functions.</p>
+ </li>
+ <li>
+ <p>Maintains an histogram of currently opened incidents on this rack.</p>
+ </li>
+ <li>
+ <p>Applies a correlation model to the individual incidents sent by the <strong>ServerFun</strong>, and reports high-level, related incidents as a single incident to the <strong>DataCenterFun</strong>.</p>
+ </li>
+</ol>
+
+<p><strong>DataCenterFun</strong></p>
+
+<p>This function maintains a view of incidents across different racks in our datacenter.</p>
+
+<div style="line-height:60%;">
+ <br />
+</div>
+
+<center>
+<img src="/img/blog/2020-08-18-statefun/2.png" width="600px" alt="" />
+</center>
+
+<div style="line-height:60%;">
+ <br />
+</div>
+
+<p>To summarize our plan:</p>
+
+<ul>
+ <li>
+ <p>Leaf functions ingest raw metric data (<span style="color:blue">blue</span> lines), and apply localized logic to trigger an alert.</p>
+ </li>
+ <li>
+ <p>Intermediate functions operate on already summarized events (<span style="color:orange">orange</span> lines) and correlate them into high-level events.</p>
+ </li>
+ <li>
+ <p>A root function correlates the high-level events across the intermediate functions and into a single <em>healthy/not healthy</em> value.</p>
+ </li>
+</ul>
+
+<h2 id="how-does-it-really-look">How does it really look?</h2>
+
+<h3 id="serverfun">ServerFun</h3>
+
+<center>
+<img src="/img/blog/2020-08-18-statefun/3_1.png" width="600px" alt="" />
+</center>
+
+<div style="line-height:60%;">
+ <br />
+</div>
+
+<ol>
+ <li>This section associates a behaviour for every message that the function expects to be invoked with.</li>
+ <li>The <code>metricsHistory</code> buffer is our sliding window of the last 15 minutes worth of <code>ServerMetricReports</code>. Note that this buffer is configured to expire entries 15 minutes after they were written.</li>
+ <li><code>serverHealthState</code> represents the current physical server state, open incidents and so on.</li>
+</ol>
+
+<p>Let’s take a look at what happens when a <code>ServerMetricReport</code> message arrives:</p>
+
+<center>
+<img src="/img/blog/2020-08-18-statefun/3_2.png" width="600px" alt="" />
+</center>
+
+<div style="line-height:60%;">
+ <br />
+</div>
+
+<ol>
+ <li>Retrieve the previously computed <code>serverHealthState</code> that is kept in state.</li>
+ <li>Evaluate a model on the sliding window of the previous metric reports + the current metric reported + the previously computed server state to obtain an assessment of the current server health.</li>
+ <li>If the server is not believed to be healthy, emit an alert via an alerts topic, and also send a message to our containing rack with all the open incidents that this server currently has.</li>
+</ol>
+
+<div class="alert alert-warning">
+ <p>We’ll omit the other handlers for brevity, but it’s important to mention that <b>onTimer</b> makes sure that metric reports are coming in periodically, otherwise it’d trigger an alert stating that we didn’t hear from that server for a long time.</p>
+</div>
+
+<h3 id="rackfun">RackFun</h3>
+
+<center>
+<img src="/img/blog/2020-08-18-statefun/5.png" width="650px" alt="" />
+</center>
+
+<div style="line-height:60%;">
+ <br />
+</div>
+
+<ol>
+ <li>This function keeps a mapping between a <code>ServerId</code> and a set of open incidents on that server.</li>
+ <li>When new alerts are received, this function tries to correlate the alert with any other open alerts on that rack. If a correlated rack alert is present, this function notifies the <strong>DataCenterFun</strong> about it.</li>
+</ol>
+
+<h3 id="datacenterfun">DataCenterFun</h3>
+
+<center>
+<img src="/img/blog/2020-08-18-statefun/6.png" width="650px" alt="" />
+</center>
+
+<div style="line-height:60%;">
+ <br />
+</div>
+
+<ol>
+ <li>A persisted mapping between a <code>RackId</code> and the latest alert that rack reported.</li>
+ <li>Throughout the usage of ingress/egress pairs, this function can report back its current view of the world of what racks are currently known to be unhealthy.</li>
+ <li>An operator (via a front-end) can send a <code>GetUnhealthyRacks</code> message addressed to that <strong>DataCenterFun</strong>, and wait for the corresponding response <code>message(UnhealthyRacks)</code>. Whenever a rack reports <em>OK</em>, it’ll be removed from the unhealthy racks map.</li>
+</ol>
+
+<h2 id="conclusion">Conclusion</h2>
+
+<p>This pattern — where each layer of functions performs a stateful aggregation of events sent from the previous layer (or the input) — is useful for a whole class of problems. And, although we used connected devices to motivate this use case, it’s not limited to the IoT domain.</p>
+
+<center>
+<img src="/img/blog/2020-08-18-statefun/7.png" width="500px" alt="" />
+</center>
+
+<div style="line-height:60%;">
+ <br />
+</div>
+
+<p>Stateful Functions provides the building blocks necessary for building complex distributed applications (here the digital twins that support analysis and interactions of the physical entities), while removing common complexities of distributed systems like service discovery, retires, circuit breakers, state management, scalability and similar challenges. If you’d like to learn more about Stateful Functions, head over to the official <a href="https://ci.apache.org/project [...]
+</description>
+<pubDate>Wed, 19 Aug 2020 10:00:00 +0200</pubDate>
+<link>https://flink.apache.org/2020/08/19/statefun.html</link>
+<guid isPermaLink="true">/2020/08/19/statefun.html</guid>
+</item>
+
+<item>
<title>Accelerating your workload with GPU and other external resources</title>
<description><p>Apache Flink 1.11 introduces a new <a href="https://ci.apache.org/projects/flink/flink-docs-master/ops/external_resources.html">External Resource Framework</a>,
which allows you to request external resources from the underlying resource management systems (e.g., Kubernetes) and accelerate your workload with
@@ -17155,42 +17374,5 @@ When using this backend, active state in streaming programs can grow well beyond
<guid isPermaLink="true">/news/2016/03/08/release-1.0.0.html</guid>
</item>
-<item>
-<title>Flink 0.10.2 Released</title>
-<description><p>Today, the Flink community released Flink version <strong>0.10.2</strong>, the second bugfix release of the 0.10 series.</p>
-
-<p>We <strong>recommend all users updating to this release</strong> by bumping the version of your Flink dependencies to <code>0.10.2</code> and updating the binaries on the server.</p>
-
-<h2 id="issues-fixed">Issues fixed</h2>
-
-<ul>
- <li><a href="https://issues.apache.org/jira/browse/FLINK-3242">FLINK-3242</a>: Adjust StateBackendITCase for 0.10 signatures of state backends</li>
- <li><a href="https://issues.apache.org/jira/browse/FLINK-3236">FLINK-3236</a>: Flink user code classloader as parent classloader from Flink core classes</li>
- <li><a href="https://issues.apache.org/jira/browse/FLINK-2962">FLINK-2962</a>: Cluster startup script refers to unused variable</li>
- <li><a href="https://issues.apache.org/jira/browse/FLINK-3151">FLINK-3151</a>: Downgrade to Netty version 4.0.27.Final</li>
- <li><a href="https://issues.apache.org/jira/browse/FLINK-3224">FLINK-3224</a>: Call setInputType() on output formats that implement InputTypeConfigurable</li>
- <li><a href="https://issues.apache.org/jira/browse/FLINK-3218">FLINK-3218</a>: Fix overriding of user parameters when merging Hadoop configurations</li>
- <li><a href="https://issues.apache.org/jira/browse/FLINK-3189">FLINK-3189</a>: Fix argument parsing of CLI client INFO action</li>
- <li><a href="https://issues.apache.org/jira/browse/FLINK-3176">FLINK-3176</a>: Improve documentation for window apply</li>
- <li><a href="https://issues.apache.org/jira/browse/FLINK-3185">FLINK-3185</a>: Log error on failure during recovery</li>
- <li><a href="https://issues.apache.org/jira/browse/FLINK-3185">FLINK-3185</a>: Don’t swallow test failure Exception</li>
- <li><a href="https://issues.apache.org/jira/browse/FLINK-3147">FLINK-3147</a>: Expose HadoopOutputFormatBase fields as protected</li>
- <li><a href="https://issues.apache.org/jira/browse/FLINK-3145">FLINK-3145</a>: Pin Kryo version of transitive dependencies</li>
- <li><a href="https://issues.apache.org/jira/browse/FLINK-3143">FLINK-3143</a>: Update Closure Cleaner’s ASM references to ASM5</li>
- <li><a href="https://issues.apache.org/jira/browse/FLINK-3136">FLINK-3136</a>: Fix shaded imports in ClosureCleaner.scala</li>
- <li><a href="https://issues.apache.org/jira/browse/FLINK-3108">FLINK-3108</a>: JoinOperator’s with() calls the wrong TypeExtractor method</li>
- <li><a href="https://issues.apache.org/jira/browse/FLINK-3125">FLINK-3125</a>: Web server starts also when JobManager log files cannot be accessed.</li>
- <li><a href="https://issues.apache.org/jira/browse/FLINK-3080">FLINK-3080</a>: Relax restrictions of DataStream.union()</li>
- <li><a href="https://issues.apache.org/jira/browse/FLINK-3081">FLINK-3081</a>: Properly stop periodic Kafka committer</li>
- <li><a href="https://issues.apache.org/jira/browse/FLINK-3082">FLINK-3082</a>: Fixed confusing error about an interface that no longer exists</li>
- <li><a href="https://issues.apache.org/jira/browse/FLINK-3067">FLINK-3067</a>: Enforce zkclient 0.7 for Kafka</li>
- <li><a href="https://issues.apache.org/jira/browse/FLINK-3020">FLINK-3020</a>: Set number of task slots to maximum parallelism in local execution</li>
-</ul>
-</description>
-<pubDate>Thu, 11 Feb 2016 09:00:00 +0100</pubDate>
-<link>https://flink.apache.org/news/2016/02/11/release-0.10.2.html</link>
-<guid isPermaLink="true">/news/2016/02/11/release-0.10.2.html</guid>
-</item>
-
</channel>
</rss>
diff --git a/content/blog/index.html b/content/blog/index.html
index 222f582..7b9a744 100644
--- a/content/blog/index.html
+++ b/content/blog/index.html
@@ -196,6 +196,21 @@
<!-- Blog posts -->
<article>
+ <h2 class="blog-title"><a href="/2020/08/19/statefun.html">Monitoring and Controlling Networks of IoT Devices with Flink Stateful Functions</a></h2>
+
+ <p>19 Aug 2020
+ Igal Shilman (<a href="https://twitter.com/IgalShilman">@IgalShilman</a>)</p>
+
+ <p><p>In this blog post, we’ll take a look at a class of use cases that is a natural fit for <a href="https://flink.apache.org/stateful-functions.html">Flink Stateful Functions</a>: monitoring and controlling networks of connected devices (often called the “Internet of Things” (IoT)).</p>
+
+</p>
+
+ <p><a href="/2020/08/19/statefun.html">Continue reading »</a></p>
+ </article>
+
+ <hr>
+
+ <article>
<h2 class="blog-title"><a href="/news/2020/08/06/external-resource.html">Accelerating your workload with GPU and other external resources</a></h2>
<p>06 Aug 2020
@@ -323,22 +338,6 @@ illustrate this trend.</p>
<hr>
- <article>
- <h2 class="blog-title"><a href="/ecosystem/2020/06/23/flink-on-zeppelin-part2.html">Flink on Zeppelin Notebooks for Interactive Data Analysis - Part 2</a></h2>
-
- <p>23 Jun 2020
- Jeff Zhang (<a href="https://twitter.com/zjffdu">@zjffdu</a>)</p>
-
- <p><p>In a previous post, we introduced the basics of Flink on Zeppelin and how to do Streaming ETL. In this second part of the “Flink on Zeppelin” series of posts, I will share how to
-perform streaming data visualization via Flink on Zeppelin and how to use Apache Flink UDFs in Zeppelin.</p>
-
-</p>
-
- <p><a href="/ecosystem/2020/06/23/flink-on-zeppelin-part2.html">Continue reading »</a></p>
- </article>
-
- <hr>
-
<!-- Pagination links -->
@@ -371,6 +370,16 @@ perform streaming data visualization via Flink on Zeppelin and how to use Apache
<ul id="markdown-toc">
+ <li><a href="/2020/08/19/statefun.html">Monitoring and Controlling Networks of IoT Devices with Flink Stateful Functions</a></li>
+
+
+
+
+
+
+
+
+
<li><a href="/news/2020/08/06/external-resource.html">Accelerating your workload with GPU and other external resources</a></li>
diff --git a/content/blog/page10/index.html b/content/blog/page10/index.html
index f5127c9..441b638 100644
--- a/content/blog/page10/index.html
+++ b/content/blog/page10/index.html
@@ -196,6 +196,21 @@
<!-- Blog posts -->
<article>
+ <h2 class="blog-title"><a href="/news/2016/08/24/ff16-keynotes-panels.html">Flink Forward 2016: Announcing Schedule, Keynotes, and Panel Discussion</a></h2>
+
+ <p>24 Aug 2016
+ </p>
+
+ <p><p>An update for the Flink community: the <a href="http://flink-forward.org/kb_day/day-1/">Flink Forward 2016 schedule</a> is now available online. This year's event will include 2 days of talks from stream processing experts at Google, MapR, Alibaba, Netflix, Cloudera, and more. Following the talks is a full day of hands-on Flink training.</p>
+
+</p>
+
+ <p><a href="/news/2016/08/24/ff16-keynotes-panels.html">Continue reading »</a></p>
+ </article>
+
+ <hr>
+
+ <article>
<h2 class="blog-title"><a href="/news/2016/08/11/release-1.1.1.html">Flink 1.1.1 Released</a></h2>
<p>11 Aug 2016
@@ -327,21 +342,6 @@
<hr>
- <article>
- <h2 class="blog-title"><a href="/news/2016/02/11/release-0.10.2.html">Flink 0.10.2 Released</a></h2>
-
- <p>11 Feb 2016
- </p>
-
- <p><p>Today, the Flink community released Flink version <strong>0.10.2</strong>, the second bugfix release of the 0.10 series.</p>
-
-</p>
-
- <p><a href="/news/2016/02/11/release-0.10.2.html">Continue reading »</a></p>
- </article>
-
- <hr>
-
<!-- Pagination links -->
@@ -374,6 +374,16 @@
<ul id="markdown-toc">
+ <li><a href="/2020/08/19/statefun.html">Monitoring and Controlling Networks of IoT Devices with Flink Stateful Functions</a></li>
+
+
+
+
+
+
+
+
+
<li><a href="/news/2020/08/06/external-resource.html">Accelerating your workload with GPU and other external resources</a></li>
diff --git a/content/blog/page11/index.html b/content/blog/page11/index.html
index 70b8c8f..e8fe4c9 100644
--- a/content/blog/page11/index.html
+++ b/content/blog/page11/index.html
@@ -196,6 +196,21 @@
<!-- Blog posts -->
<article>
+ <h2 class="blog-title"><a href="/news/2016/02/11/release-0.10.2.html">Flink 0.10.2 Released</a></h2>
+
+ <p>11 Feb 2016
+ </p>
+
+ <p><p>Today, the Flink community released Flink version <strong>0.10.2</strong>, the second bugfix release of the 0.10 series.</p>
+
+</p>
+
+ <p><a href="/news/2016/02/11/release-0.10.2.html">Continue reading »</a></p>
+ </article>
+
+ <hr>
+
+ <article>
<h2 class="blog-title"><a href="/news/2015/12/18/a-year-in-review.html">Flink 2015: A year in review, and a lookout to 2016</a></h2>
<p>18 Dec 2015 by Robert Metzger (<a href="https://twitter.com/">@rmetzger_</a>)
@@ -331,21 +346,6 @@ vertex-centric or gather-sum-apply to Flink dataflows.</p>
<hr>
- <article>
- <h2 class="blog-title"><a href="/news/2015/06/24/announcing-apache-flink-0.9.0-release.html">Announcing Apache Flink 0.9.0</a></h2>
-
- <p>24 Jun 2015
- </p>
-
- <p><p>The Apache Flink community is pleased to announce the availability of the 0.9.0 release. The release is the result of many months of hard work within the Flink community. It contains many new features and improvements which were previewed in the 0.9.0-milestone1 release and have been polished since then. This is the largest Flink release so far.</p>
-
-</p>
-
- <p><a href="/news/2015/06/24/announcing-apache-flink-0.9.0-release.html">Continue reading »</a></p>
- </article>
-
- <hr>
-
<!-- Pagination links -->
@@ -378,6 +378,16 @@ vertex-centric or gather-sum-apply to Flink dataflows.</p>
<ul id="markdown-toc">
+ <li><a href="/2020/08/19/statefun.html">Monitoring and Controlling Networks of IoT Devices with Flink Stateful Functions</a></li>
+
+
+
+
+
+
+
+
+
<li><a href="/news/2020/08/06/external-resource.html">Accelerating your workload with GPU and other external resources</a></li>
diff --git a/content/blog/page12/index.html b/content/blog/page12/index.html
index 9c38ad9..fc5157a 100644
--- a/content/blog/page12/index.html
+++ b/content/blog/page12/index.html
@@ -196,6 +196,21 @@
<!-- Blog posts -->
<article>
+ <h2 class="blog-title"><a href="/news/2015/06/24/announcing-apache-flink-0.9.0-release.html">Announcing Apache Flink 0.9.0</a></h2>
+
+ <p>24 Jun 2015
+ </p>
+
+ <p><p>The Apache Flink community is pleased to announce the availability of the 0.9.0 release. The release is the result of many months of hard work within the Flink community. It contains many new features and improvements which were previewed in the 0.9.0-milestone1 release and have been polished since then. This is the largest Flink release so far.</p>
+
+</p>
+
+ <p><a href="/news/2015/06/24/announcing-apache-flink-0.9.0-release.html">Continue reading »</a></p>
+ </article>
+
+ <hr>
+
+ <article>
<h2 class="blog-title"><a href="/news/2015/05/14/Community-update-April.html">April 2015 in the Flink community</a></h2>
<p>14 May 2015 by Kostas Tzoumas (<a href="https://twitter.com/">@kostas_tzoumas</a>)
@@ -337,21 +352,6 @@ and offers a new API including definition of flexible windows.</p>
<hr>
- <article>
- <h2 class="blog-title"><a href="/news/2015/01/06/december-in-flink.html">December 2014 in the Flink community</a></h2>
-
- <p>06 Jan 2015
- </p>
-
- <p><p>This is the first blog post of a “newsletter” like series where we give a summary of the monthly activity in the Flink community. As the Flink project grows, this can serve as a “tl;dr” for people that are not following the Flink dev and user mailing lists, or those that are simply overwhelmed by the traffic.</p>
-
-</p>
-
- <p><a href="/news/2015/01/06/december-in-flink.html">Continue reading »</a></p>
- </article>
-
- <hr>
-
<!-- Pagination links -->
@@ -384,6 +384,16 @@ and offers a new API including definition of flexible windows.</p>
<ul id="markdown-toc">
+ <li><a href="/2020/08/19/statefun.html">Monitoring and Controlling Networks of IoT Devices with Flink Stateful Functions</a></li>
+
+
+
+
+
+
+
+
+
<li><a href="/news/2020/08/06/external-resource.html">Accelerating your workload with GPU and other external resources</a></li>
diff --git a/content/blog/page13/index.html b/content/blog/page13/index.html
index 1e6a993..97d47e9 100644
--- a/content/blog/page13/index.html
+++ b/content/blog/page13/index.html
@@ -196,6 +196,21 @@
<!-- Blog posts -->
<article>
+ <h2 class="blog-title"><a href="/news/2015/01/06/december-in-flink.html">December 2014 in the Flink community</a></h2>
+
+ <p>06 Jan 2015
+ </p>
+
+ <p><p>This is the first blog post of a “newsletter” like series where we give a summary of the monthly activity in the Flink community. As the Flink project grows, this can serve as a “tl;dr” for people that are not following the Flink dev and user mailing lists, or those that are simply overwhelmed by the traffic.</p>
+
+</p>
+
+ <p><a href="/news/2015/01/06/december-in-flink.html">Continue reading »</a></p>
+ </article>
+
+ <hr>
+
+ <article>
<h2 class="blog-title"><a href="/news/2014/11/18/hadoop-compatibility.html">Hadoop Compatibility in Flink</a></h2>
<p>18 Nov 2014 by Fabian Hüske (<a href="https://twitter.com/">@fhueske</a>)
@@ -305,6 +320,16 @@ academic and open source project that Flink originates from.</p>
<ul id="markdown-toc">
+ <li><a href="/2020/08/19/statefun.html">Monitoring and Controlling Networks of IoT Devices with Flink Stateful Functions</a></li>
+
+
+
+
+
+
+
+
+
<li><a href="/news/2020/08/06/external-resource.html">Accelerating your workload with GPU and other external resources</a></li>
diff --git a/content/blog/page2/index.html b/content/blog/page2/index.html
index 09bbc9f..8183894 100644
--- a/content/blog/page2/index.html
+++ b/content/blog/page2/index.html
@@ -196,6 +196,22 @@
<!-- Blog posts -->
<article>
+ <h2 class="blog-title"><a href="/ecosystem/2020/06/23/flink-on-zeppelin-part2.html">Flink on Zeppelin Notebooks for Interactive Data Analysis - Part 2</a></h2>
+
+ <p>23 Jun 2020
+ Jeff Zhang (<a href="https://twitter.com/zjffdu">@zjffdu</a>)</p>
+
+ <p><p>In a previous post, we introduced the basics of Flink on Zeppelin and how to do Streaming ETL. In this second part of the “Flink on Zeppelin” series of posts, I will share how to
+perform streaming data visualization via Flink on Zeppelin and how to use Apache Flink UDFs in Zeppelin.</p>
+
+</p>
+
+ <p><a href="/ecosystem/2020/06/23/flink-on-zeppelin-part2.html">Continue reading »</a></p>
+ </article>
+
+ <hr>
+
+ <article>
<h2 class="blog-title"><a href="/news/2020/06/15/flink-on-zeppelin-part1.html">Flink on Zeppelin Notebooks for Interactive Data Analysis - Part 1</a></h2>
<p>15 Jun 2020
@@ -322,19 +338,6 @@ and provide a tutorial for running Streaming ETL with Flink on Zeppelin.</p>
<hr>
- <article>
- <h2 class="blog-title"><a href="/2020/04/09/pyflink-udf-support-flink.html">PyFlink: Introducing Python Support for UDFs in Flink's Table API</a></h2>
-
- <p>09 Apr 2020
- Jincheng Sun (<a href="https://twitter.com/sunjincheng121">@sunjincheng121</a>) & Markos Sfikas (<a href="https://twitter.com/MarkSfik">@MarkSfik</a>)</p>
-
- <p>Flink 1.10 extends its support for Python by adding Python UDFs in PyFlink. This post explains how UDFs work in PyFlink and gives some practical examples of how to use UDFs in PyFlink.</p>
-
- <p><a href="/2020/04/09/pyflink-udf-support-flink.html">Continue reading »</a></p>
- </article>
-
- <hr>
-
<!-- Pagination links -->
@@ -367,6 +370,16 @@ and provide a tutorial for running Streaming ETL with Flink on Zeppelin.</p>
<ul id="markdown-toc">
+ <li><a href="/2020/08/19/statefun.html">Monitoring and Controlling Networks of IoT Devices with Flink Stateful Functions</a></li>
+
+
+
+
+
+
+
+
+
<li><a href="/news/2020/08/06/external-resource.html">Accelerating your workload with GPU and other external resources</a></li>
diff --git a/content/blog/page3/index.html b/content/blog/page3/index.html
index 57b70d9..540a29b 100644
--- a/content/blog/page3/index.html
+++ b/content/blog/page3/index.html
@@ -196,6 +196,19 @@
<!-- Blog posts -->
<article>
+ <h2 class="blog-title"><a href="/2020/04/09/pyflink-udf-support-flink.html">PyFlink: Introducing Python Support for UDFs in Flink's Table API</a></h2>
+
+ <p>09 Apr 2020
+ Jincheng Sun (<a href="https://twitter.com/sunjincheng121">@sunjincheng121</a>) & Markos Sfikas (<a href="https://twitter.com/MarkSfik">@MarkSfik</a>)</p>
+
+ <p>Flink 1.10 extends its support for Python by adding Python UDFs in PyFlink. This post explains how UDFs work in PyFlink and gives some practical examples of how to use UDFs in PyFlink.</p>
+
+ <p><a href="/2020/04/09/pyflink-udf-support-flink.html">Continue reading »</a></p>
+ </article>
+
+ <hr>
+
+ <article>
<h2 class="blog-title"><a href="/news/2020/04/07/release-statefun-2.0.0.html">Stateful Functions 2.0 - An Event-driven Database on Apache Flink</a></h2>
<p>07 Apr 2020
@@ -321,19 +334,6 @@ This release marks a big milestone: Stateful Functions 2.0 is not only an API up
<hr>
- <article>
- <h2 class="blog-title"><a href="/news/2020/01/29/state-unlocked-interacting-with-state-in-apache-flink.html">State Unlocked: Interacting with State in Apache Flink</a></h2>
-
- <p>29 Jan 2020
- Seth Wiesman (<a href="https://twitter.com/sjwiesman">@sjwiesman</a>)</p>
-
- <p>This post discusses the efforts of the Flink community as they relate to state management in Apache Flink. We showcase some practical examples of how the different features and APIs can be utilized and cover some future ideas for new and improved ways of managing state in Apache Flink.</p>
-
- <p><a href="/news/2020/01/29/state-unlocked-interacting-with-state-in-apache-flink.html">Continue reading »</a></p>
- </article>
-
- <hr>
-
<!-- Pagination links -->
@@ -366,6 +366,16 @@ This release marks a big milestone: Stateful Functions 2.0 is not only an API up
<ul id="markdown-toc">
+ <li><a href="/2020/08/19/statefun.html">Monitoring and Controlling Networks of IoT Devices with Flink Stateful Functions</a></li>
+
+
+
+
+
+
+
+
+
<li><a href="/news/2020/08/06/external-resource.html">Accelerating your workload with GPU and other external resources</a></li>
diff --git a/content/blog/page4/index.html b/content/blog/page4/index.html
index a3fbf0e..603493b 100644
--- a/content/blog/page4/index.html
+++ b/content/blog/page4/index.html
@@ -196,6 +196,19 @@
<!-- Blog posts -->
<article>
+ <h2 class="blog-title"><a href="/news/2020/01/29/state-unlocked-interacting-with-state-in-apache-flink.html">State Unlocked: Interacting with State in Apache Flink</a></h2>
+
+ <p>29 Jan 2020
+ Seth Wiesman (<a href="https://twitter.com/sjwiesman">@sjwiesman</a>)</p>
+
+ <p>This post discusses the efforts of the Flink community as they relate to state management in Apache Flink. We showcase some practical examples of how the different features and APIs can be utilized and cover some future ideas for new and improved ways of managing state in Apache Flink.</p>
+
+ <p><a href="/news/2020/01/29/state-unlocked-interacting-with-state-in-apache-flink.html">Continue reading »</a></p>
+ </article>
+
+ <hr>
+
+ <article>
<h2 class="blog-title"><a href="/news/2020/01/15/demo-fraud-detection.html">Advanced Flink Application Patterns Vol.1: Case Study of a Fraud Detection System</a></h2>
<p>15 Jan 2020
@@ -321,19 +334,6 @@
<hr>
- <article>
- <h2 class="blog-title"><a href="/2019/07/23/flink-network-stack-2.html">Flink Network Stack Vol. 2: Monitoring, Metrics, and that Backpressure Thing</a></h2>
-
- <p>23 Jul 2019
- Nico Kruber & Piotr Nowojski </p>
-
- <p>In a previous blog post, we presented how Flink’s network stack works from the high-level abstractions to the low-level details. This second post discusses monitoring network-related metrics to identify backpressure or bottlenecks in throughput and latency.</p>
-
- <p><a href="/2019/07/23/flink-network-stack-2.html">Continue reading »</a></p>
- </article>
-
- <hr>
-
<!-- Pagination links -->
@@ -366,6 +366,16 @@
<ul id="markdown-toc">
+ <li><a href="/2020/08/19/statefun.html">Monitoring and Controlling Networks of IoT Devices with Flink Stateful Functions</a></li>
+
+
+
+
+
+
+
+
+
<li><a href="/news/2020/08/06/external-resource.html">Accelerating your workload with GPU and other external resources</a></li>
diff --git a/content/blog/page5/index.html b/content/blog/page5/index.html
index 61cc1a9..97a63ec 100644
--- a/content/blog/page5/index.html
+++ b/content/blog/page5/index.html
@@ -196,6 +196,19 @@
<!-- Blog posts -->
<article>
+ <h2 class="blog-title"><a href="/2019/07/23/flink-network-stack-2.html">Flink Network Stack Vol. 2: Monitoring, Metrics, and that Backpressure Thing</a></h2>
+
+ <p>23 Jul 2019
+ Nico Kruber & Piotr Nowojski </p>
+
+ <p>In a previous blog post, we presented how Flink’s network stack works from the high-level abstractions to the low-level details. This second post discusses monitoring network-related metrics to identify backpressure or bottlenecks in throughput and latency.</p>
+
+ <p><a href="/2019/07/23/flink-network-stack-2.html">Continue reading »</a></p>
+ </article>
+
+ <hr>
+
+ <article>
<h2 class="blog-title"><a href="/news/2019/07/02/release-1.8.1.html">Apache Flink 1.8.1 Released</a></h2>
<p>02 Jul 2019
@@ -322,19 +335,6 @@ for more details.</p>
<hr>
- <article>
- <h2 class="blog-title"><a href="/news/2019/03/06/ffsf-preview.html">What to expect from Flink Forward San Francisco 2019</a></h2>
-
- <p>06 Mar 2019
- Fabian Hueske (<a href="https://twitter.com/fhueske">@fhueske</a>)</p>
-
- <p>The third annual Flink Forward conference in San Francisco is just a few weeks away. Let's see what Flink Forward SF 2019 has in store for the Apache Flink and stream processing communities. This post covers some of its highlights!</p>
-
- <p><a href="/news/2019/03/06/ffsf-preview.html">Continue reading »</a></p>
- </article>
-
- <hr>
-
<!-- Pagination links -->
@@ -367,6 +367,16 @@ for more details.</p>
<ul id="markdown-toc">
+ <li><a href="/2020/08/19/statefun.html">Monitoring and Controlling Networks of IoT Devices with Flink Stateful Functions</a></li>
+
+
+
+
+
+
+
+
+
<li><a href="/news/2020/08/06/external-resource.html">Accelerating your workload with GPU and other external resources</a></li>
diff --git a/content/blog/page6/index.html b/content/blog/page6/index.html
index 855fbcd..2a7bf4e 100644
--- a/content/blog/page6/index.html
+++ b/content/blog/page6/index.html
@@ -196,6 +196,19 @@
<!-- Blog posts -->
<article>
+ <h2 class="blog-title"><a href="/news/2019/03/06/ffsf-preview.html">What to expect from Flink Forward San Francisco 2019</a></h2>
+
+ <p>06 Mar 2019
+ Fabian Hueske (<a href="https://twitter.com/fhueske">@fhueske</a>)</p>
+
+ <p>The third annual Flink Forward conference in San Francisco is just a few weeks away. Let's see what Flink Forward SF 2019 has in store for the Apache Flink and stream processing communities. This post covers some of its highlights!</p>
+
+ <p><a href="/news/2019/03/06/ffsf-preview.html">Continue reading »</a></p>
+ </article>
+
+ <hr>
+
+ <article>
<h2 class="blog-title"><a href="/news/2019/02/25/monitoring-best-practices.html">Monitoring Apache Flink Applications 101</a></h2>
<p>25 Feb 2019
@@ -328,21 +341,6 @@ Please check the <a href="https://issues.apache.org/jira/secure/ReleaseNote.jspa
<hr>
- <article>
- <h2 class="blog-title"><a href="/news/2018/10/29/release-1.5.5.html">Apache Flink 1.5.5 Released</a></h2>
-
- <p>29 Oct 2018
- </p>
-
- <p><p>The Apache Flink community released the fifth bugfix version of the Apache Flink 1.5 series.</p>
-
-</p>
-
- <p><a href="/news/2018/10/29/release-1.5.5.html">Continue reading »</a></p>
- </article>
-
- <hr>
-
<!-- Pagination links -->
@@ -375,6 +373,16 @@ Please check the <a href="https://issues.apache.org/jira/secure/ReleaseNote.jspa
<ul id="markdown-toc">
+ <li><a href="/2020/08/19/statefun.html">Monitoring and Controlling Networks of IoT Devices with Flink Stateful Functions</a></li>
+
+
+
+
+
+
+
+
+
<li><a href="/news/2020/08/06/external-resource.html">Accelerating your workload with GPU and other external resources</a></li>
diff --git a/content/blog/page7/index.html b/content/blog/page7/index.html
index b89617d..f9d3b07 100644
--- a/content/blog/page7/index.html
+++ b/content/blog/page7/index.html
@@ -196,6 +196,21 @@
<!-- Blog posts -->
<article>
+ <h2 class="blog-title"><a href="/news/2018/10/29/release-1.5.5.html">Apache Flink 1.5.5 Released</a></h2>
+
+ <p>29 Oct 2018
+ </p>
+
+ <p><p>The Apache Flink community released the fifth bugfix version of the Apache Flink 1.5 series.</p>
+
+</p>
+
+ <p><a href="/news/2018/10/29/release-1.5.5.html">Continue reading »</a></p>
+ </article>
+
+ <hr>
+
+ <article>
<h2 class="blog-title"><a href="/news/2018/09/20/release-1.6.1.html">Apache Flink 1.6.1 Released</a></h2>
<p>20 Sep 2018
@@ -330,19 +345,6 @@
<hr>
- <article>
- <h2 class="blog-title"><a href="/features/2018/03/01/end-to-end-exactly-once-apache-flink.html">An Overview of End-to-End Exactly-Once Processing in Apache Flink (with Apache Kafka, too!)</a></h2>
-
- <p>01 Mar 2018
- Piotr Nowojski (<a href="https://twitter.com/PiotrNowojski">@PiotrNowojski</a>) & Mike Winters (<a href="https://twitter.com/wints">@wints</a>)</p>
-
- <p>Flink 1.4.0 introduced a new feature that makes it possible to build end-to-end exactly-once applications with Flink and data sources and sinks that support transactions.</p>
-
- <p><a href="/features/2018/03/01/end-to-end-exactly-once-apache-flink.html">Continue reading »</a></p>
- </article>
-
- <hr>
-
<!-- Pagination links -->
@@ -375,6 +377,16 @@
<ul id="markdown-toc">
+ <li><a href="/2020/08/19/statefun.html">Monitoring and Controlling Networks of IoT Devices with Flink Stateful Functions</a></li>
+
+
+
+
+
+
+
+
+
<li><a href="/news/2020/08/06/external-resource.html">Accelerating your workload with GPU and other external resources</a></li>
diff --git a/content/blog/page8/index.html b/content/blog/page8/index.html
index 1b4a7be..32220cd 100644
--- a/content/blog/page8/index.html
+++ b/content/blog/page8/index.html
@@ -196,6 +196,19 @@
<!-- Blog posts -->
<article>
+ <h2 class="blog-title"><a href="/features/2018/03/01/end-to-end-exactly-once-apache-flink.html">An Overview of End-to-End Exactly-Once Processing in Apache Flink (with Apache Kafka, too!)</a></h2>
+
+ <p>01 Mar 2018
+ Piotr Nowojski (<a href="https://twitter.com/PiotrNowojski">@PiotrNowojski</a>) & Mike Winters (<a href="https://twitter.com/wints">@wints</a>)</p>
+
+ <p>Flink 1.4.0 introduced a new feature that makes it possible to build end-to-end exactly-once applications with Flink and data sources and sinks that support transactions.</p>
+
+ <p><a href="/features/2018/03/01/end-to-end-exactly-once-apache-flink.html">Continue reading »</a></p>
+ </article>
+
+ <hr>
+
+ <article>
<h2 class="blog-title"><a href="/news/2018/02/15/release-1.4.1.html">Apache Flink 1.4.1 Released</a></h2>
<p>15 Feb 2018
@@ -329,21 +342,6 @@ what’s coming in Flink 1.4.0 as well as a preview of what the Flink community
<hr>
- <article>
- <h2 class="blog-title"><a href="/news/2017/05/16/official-docker-image.html">Introducing Docker Images for Apache Flink</a></h2>
-
- <p>16 May 2017 by Patrick Lucas (Data Artisans) and Ismaël Mejía (Talend) (<a href="https://twitter.com/">@iemejia</a>)
- </p>
-
- <p><p>For some time, the Apache Flink community has provided scripts to build a Docker image to run Flink. Now, starting with version 1.2.1, Flink will have a <a href="https://hub.docker.com/r/_/flink/">Docker image</a> on the Docker Hub. This image is maintained by the Flink community and curated by the <a href="https://github.com/docker-library/official-images">Docker</a> team to ensure it meets the quality standards for container images of the Docker community.</p>
-
-</p>
-
- <p><a href="/news/2017/05/16/official-docker-image.html">Continue reading »</a></p>
- </article>
-
- <hr>
-
<!-- Pagination links -->
@@ -376,6 +374,16 @@ what’s coming in Flink 1.4.0 as well as a preview of what the Flink community
<ul id="markdown-toc">
+ <li><a href="/2020/08/19/statefun.html">Monitoring and Controlling Networks of IoT Devices with Flink Stateful Functions</a></li>
+
+
+
+
+
+
+
+
+
<li><a href="/news/2020/08/06/external-resource.html">Accelerating your workload with GPU and other external resources</a></li>
diff --git a/content/blog/page9/index.html b/content/blog/page9/index.html
index 67691c2..ae101ea 100644
--- a/content/blog/page9/index.html
+++ b/content/blog/page9/index.html
@@ -196,6 +196,21 @@
<!-- Blog posts -->
<article>
+ <h2 class="blog-title"><a href="/news/2017/05/16/official-docker-image.html">Introducing Docker Images for Apache Flink</a></h2>
+
+ <p>16 May 2017 by Patrick Lucas (Data Artisans) and Ismaël Mejía (Talend) (<a href="https://twitter.com/">@iemejia</a>)
+ </p>
+
+ <p><p>For some time, the Apache Flink community has provided scripts to build a Docker image to run Flink. Now, starting with version 1.2.1, Flink will have a <a href="https://hub.docker.com/r/_/flink/">Docker image</a> on the Docker Hub. This image is maintained by the Flink community and curated by the <a href="https://github.com/docker-library/official-images">Docker</a> team to ensure it meets the quality standards for container images of the Docker community.</p>
+
+</p>
+
+ <p><a href="/news/2017/05/16/official-docker-image.html">Continue reading »</a></p>
+ </article>
+
+ <hr>
+
+ <article>
<h2 class="blog-title"><a href="/news/2017/04/26/release-1.2.1.html">Apache Flink 1.2.1 Released</a></h2>
<p>26 Apr 2017
@@ -323,21 +338,6 @@
<hr>
- <article>
- <h2 class="blog-title"><a href="/news/2016/08/24/ff16-keynotes-panels.html">Flink Forward 2016: Announcing Schedule, Keynotes, and Panel Discussion</a></h2>
-
- <p>24 Aug 2016
- </p>
-
- <p><p>An update for the Flink community: the <a href="http://flink-forward.org/kb_day/day-1/">Flink Forward 2016 schedule</a> is now available online. This year's event will include 2 days of talks from stream processing experts at Google, MapR, Alibaba, Netflix, Cloudera, and more. Following the talks is a full day of hands-on Flink training.</p>
-
-</p>
-
- <p><a href="/news/2016/08/24/ff16-keynotes-panels.html">Continue reading »</a></p>
- </article>
-
- <hr>
-
<!-- Pagination links -->
@@ -370,6 +370,16 @@
<ul id="markdown-toc">
+ <li><a href="/2020/08/19/statefun.html">Monitoring and Controlling Networks of IoT Devices with Flink Stateful Functions</a></li>
+
+
+
+
+
+
+
+
+
<li><a href="/news/2020/08/06/external-resource.html">Accelerating your workload with GPU and other external resources</a></li>
diff --git a/content/img/blog/2020-08-18-statefun/1.png b/content/img/blog/2020-08-18-statefun/1.png
new file mode 100755
index 0000000..87f880d
Binary files /dev/null and b/content/img/blog/2020-08-18-statefun/1.png differ
diff --git a/content/img/blog/2020-08-18-statefun/2.png b/content/img/blog/2020-08-18-statefun/2.png
new file mode 100755
index 0000000..3543f31
Binary files /dev/null and b/content/img/blog/2020-08-18-statefun/2.png differ
diff --git a/content/img/blog/2020-08-18-statefun/3_1.png b/content/img/blog/2020-08-18-statefun/3_1.png
new file mode 100755
index 0000000..b3aa0c0
Binary files /dev/null and b/content/img/blog/2020-08-18-statefun/3_1.png differ
diff --git a/content/img/blog/2020-08-18-statefun/3_2.png b/content/img/blog/2020-08-18-statefun/3_2.png
new file mode 100755
index 0000000..30d4857
Binary files /dev/null and b/content/img/blog/2020-08-18-statefun/3_2.png differ
diff --git a/content/img/blog/2020-08-18-statefun/5.png b/content/img/blog/2020-08-18-statefun/5.png
new file mode 100755
index 0000000..aeab5cf
Binary files /dev/null and b/content/img/blog/2020-08-18-statefun/5.png differ
diff --git a/content/img/blog/2020-08-18-statefun/6.png b/content/img/blog/2020-08-18-statefun/6.png
new file mode 100755
index 0000000..38589f7
Binary files /dev/null and b/content/img/blog/2020-08-18-statefun/6.png differ
diff --git a/content/img/blog/2020-08-18-statefun/7.png b/content/img/blog/2020-08-18-statefun/7.png
new file mode 100755
index 0000000..291324c
Binary files /dev/null and b/content/img/blog/2020-08-18-statefun/7.png differ
diff --git a/content/img/blog/2020-08-18-statefun/rack.png b/content/img/blog/2020-08-18-statefun/rack.png
new file mode 100755
index 0000000..8b9c9ff
Binary files /dev/null and b/content/img/blog/2020-08-18-statefun/rack.png differ
diff --git a/content/index.html b/content/index.html
index f6f58ae..46aed21 100644
--- a/content/index.html
+++ b/content/index.html
@@ -568,6 +568,11 @@
<dl>
+ <dt> <a href="/2020/08/19/statefun.html">Monitoring and Controlling Networks of IoT Devices with Flink Stateful Functions</a></dt>
+ <dd><p>In this blog post, we’ll take a look at a class of use cases that is a natural fit for <a href="https://flink.apache.org/stateful-functions.html">Flink Stateful Functions</a>: monitoring and controlling networks of connected devices (often called the “Internet of Things” (IoT)).</p>
+
+</dd>
+
<dt> <a href="/news/2020/08/06/external-resource.html">Accelerating your workload with GPU and other external resources</a></dt>
<dd>This post introduces the new External Resource Framework in Flink 1.11 and take GPU as an example to show how to accelerate your workload with external resources.</dd>
@@ -579,9 +584,6 @@
<dt> <a href="/2020/07/28/flink-sql-demo-building-e2e-streaming-application.html">Flink SQL Demo: Building an End-to-End Streaming Application</a></dt>
<dd>Apache Flink 1.11 has released many exciting new features, including many developments in Flink SQL which is evolving at a fast pace. This article takes a closer look at how to quickly build streaming applications with Flink SQL from a practical point of view.</dd>
-
- <dt> <a href="/news/2020/07/27/community-update.html">Flink Community Update - July'20</a></dt>
- <dd>As July draws to an end, we look back at a monthful of activity in the Flink community, including two releases (!) and some work around improving the first-time contribution experience in the project. Also, events are starting to pick up again, so we've put together a list of some great events you can (virtually) attend in August!</dd>
</dl>
diff --git a/content/zh/index.html b/content/zh/index.html
index 6656e7c..e28fda8 100644
--- a/content/zh/index.html
+++ b/content/zh/index.html
@@ -565,6 +565,11 @@
<dl>
+ <dt> <a href="/2020/08/19/statefun.html">Monitoring and Controlling Networks of IoT Devices with Flink Stateful Functions</a></dt>
+ <dd><p>In this blog post, we’ll take a look at a class of use cases that is a natural fit for <a href="https://flink.apache.org/stateful-functions.html">Flink Stateful Functions</a>: monitoring and controlling networks of connected devices (often called the “Internet of Things” (IoT)).</p>
+
+</dd>
+
<dt> <a href="/news/2020/08/06/external-resource.html">Accelerating your workload with GPU and other external resources</a></dt>
<dd>This post introduces the new External Resource Framework in Flink 1.11 and take GPU as an example to show how to accelerate your workload with external resources.</dd>
@@ -576,9 +581,6 @@
<dt> <a href="/2020/07/28/flink-sql-demo-building-e2e-streaming-application.html">Flink SQL Demo: Building an End-to-End Streaming Application</a></dt>
<dd>Apache Flink 1.11 has released many exciting new features, including many developments in Flink SQL which is evolving at a fast pace. This article takes a closer look at how to quickly build streaming applications with Flink SQL from a practical point of view.</dd>
-
- <dt> <a href="/news/2020/07/27/community-update.html">Flink Community Update - July'20</a></dt>
- <dd>As July draws to an end, we look back at a monthful of activity in the Flink community, including two releases (!) and some work around improving the first-time contribution experience in the project. Also, events are starting to pick up again, so we've put together a list of some great events you can (virtually) attend in August!</dd>
</dl>