Repository: kudu-site Updated Branches: refs/heads/asf-site b81a95b51 -> 9b3a1052c
http://git-wip-us.apache.org/repos/asf/kudu-site/blob/9b3a1052/blog/page/2/index.html ---------------------------------------------------------------------- diff --git a/blog/page/2/index.html b/blog/page/2/index.html index 47125a0..f640c39 100644 --- a/blog/page/2/index.html +++ b/blog/page/2/index.html @@ -111,6 +111,320 @@ <!-- Articles --> <article> <header> + <h1 class="entry-title"><a href="/2016/08/31/intro-flume-kudu-sink.html">An Introduction to the Flume Kudu Sink</a></h1> + <p class="meta">Posted 31 Aug 2016 by Ara Abrahamian</p> + </header> + <div class="entry-content"> + + <p>This post discusses the Kudu Flume Sink. First, I’ll give some background on why we considered +using Kudu, what Flume does for us, and how Flume fits with Kudu in our project.</p> + +<h2 id="why-kudu">Why Kudu</h2> + +<p>Traditionally in the Hadoop ecosystem we’ve dealt with various <em>batch processing</em> technologies such +as MapReduce and the many libraries and tools built on top of it in various languages (Apache Pig, +Apache Hive, Apache Oozie and many others). The main problem with this approach is that it needs to +process the whole data set in batches, again and again, as soon as new data gets added. Things get +really complicated when a few such tasks need to get chained together, or when the same data set +needs to be processed in various ways by different jobs, while all compete for the shared cluster +resources.</p> + +<p>The opposite of this approach is <em>stream processing</em>: process the data as soon as it arrives, not +in batches. Streaming systems such as Spark Streaming, Storm, Kafka Streams, and many others make +this possible. But writing streaming services is not trivial. The streaming systems are becoming +more and more capable and support more complex constructs, but they are not yet easy to use. All +queries and processes need to be carefully planned and implemented.</p> + +<p>To summarize, <em>batch processing</em> is:</p> + +<ul> + <li>file-based</li> + <li>a paradigm that processes large chunks of data as a group</li> + <li>high latency and high throughput, both for ingest and query</li> + <li>typically easy to program, but hard to orchestrate</li> + <li>well suited for writing ad-hoc queries, although they are typically high latency</li> +</ul> + +<p>While <em>stream processing</em> is:</p> + +<ul> + <li>a totally different paradigm, which involves single events and time windows instead of large groups of events</li> + <li>still file-based and not a long-term database</li> + <li>not batch-oriented, but incremental</li> + <li>ultra-fast ingest and ultra-fast query (query results basically pre-calculated)</li> + <li>not so easy to program, relatively easy to orchestrate</li> + <li>impossible to write ad-hoc queries</li> +</ul> + +<p>And a Kudu-based <em>near real-time</em> approach is:</p> + +<ul> + <li>flexible and expressive, thanks to SQL support via Apache Impala (incubating)</li> + <li>a table-oriented, mutable data store that feels like a traditional relational database</li> + <li>very easy to program, you can even pretend it’s good old MySQL</li> + <li>low-latency and relatively high throughput, both for ingest and query</li> +</ul> + +<p>At Argyle Data, we’re dealing with complex fraud detection scenarios. We need to ingest massive +amounts of data, run machine learning algorithms and generate reports. When we created our current +architecture two years ago we decided to opt for a database as the backbone of our system. That +database is Apache Accumulo. It’s a key-value based database which runs on top of Hadoop HDFS, +quite similar to HBase but with some important improvements such as cell level security and ease +of deployment and management. To enable querying of this data for quite complex reporting and +analytics, we used Presto, a distributed query engine with a pluggable architecture open-sourced +by Facebook. We wrote a connector for it to let it run queries against the Accumulo database. This +architecture has served us well, but there were a few problems:</p> + +<ul> + <li>we need to ingest even more massive volumes of data in real-time</li> + <li>we need to perform complex machine-learning calculations on even larger data-sets</li> + <li>we need to support ad-hoc queries, plus long-term data warehouse functionality</li> +</ul> + +<p>So, we’ve started gradually moving the core machine-learning pipeline to a streaming based +solution. This way we can ingest and process larger data-sets faster in the real-time. But then how +would we take care of ad-hoc queries and long-term persistence? This is where Kudu comes in. While +the machine learning pipeline ingests and processes real-time data, we store a copy of the same +ingested data in Kudu for long-term access and ad-hoc queries. Kudu is our <em>data warehouse</em>. By +using Kudu and Impala, we can retire our in-house Presto connector and rely on Impala’s +super-fast query engine.</p> + +<p>But how would we make sure data is reliably ingested into the streaming pipeline <em>and</em> the +Kudu-based data warehouse? This is where Apache Flume comes in.</p> + +<h2 id="why-flume">Why Flume</h2> + +<p>According to their <a href="http://flume.apache.org/";>website</a> “Flume is a distributed, reliable, and +available service for efficiently collecting, aggregating, and moving large amounts of log data. +It has a simple and flexible architecture based on streaming data flows. It is robust and fault +tolerant with tunable reliability mechanisms and many failover and recovery mechanisms.” As you +can see, nowhere is Hadoop mentioned but Flume is typically used for ingesting data to Hadoop +clusters.</p> + +<p><img src="https://blogs.apache.org/flume/mediaresource/ab0d50f6-a960-42cc-971e-3da38ba3adad"; alt="png" /></p> + +<p>Flume has an extensible architecture. An instance of Flume, called an <em>agent</em>, can have multiple +<em>channels</em>, with each having multiple <em>sources</em> and <em>sinks</em> of various types. Sources queue data +in channels, which in turn write out data to sinks. Such <em>pipelines</em> can be chained together to +create even more complex ones. There may be more than one agent and agents can be configured to +support failover and recovery.</p> + +<p>Flume comes with a bunch of built-in types of channels, sources and sinks. Memory channel is the +default (an in-memory queue with no persistence to disk), but other options such as Kafka- and +File-based channels are also provided. As for the sources, Avro, JMS, Thrift, spooling directory +source are some of the built-in ones. Flume also ships with many sinks, including sinks for writing +data to HDFS, HBase, Hive, Kafka, as well as to other Flume agents.</p> + +<p>In the rest of this post I’ll go over the Kudu Flume sink and show you how to configure Flume to +write ingested data to a Kudu table. The sink has been part of the Kudu distribution since the 0.8 +release and the source code can be found <a href="https://github.com/apache/kudu/tree/master/java/kudu-flume-sink";>here</a>.</p> + +<h2 id="configuring-the-kudu-flume-sink">Configuring the Kudu Flume Sink</h2> + +<p>Here is a sample flume configuration file:</p> + +<pre><code>agent1.sources = source1 +agent1.channels = channel1 +agent1.sinks = sink1 + +agent1.sources.source1.type = exec +agent1.sources.source1.command = /usr/bin/vmstat 1 +agent1.sources.source1.channels = channel1 + +agent1.channels.channel1.type = memory +agent1.channels.channel1.capacity = 10000 +agent1.channels.channel1.transactionCapacity = 1000 + +agent1.sinks.sink1.type = org.apache.flume.sink.kudu.KuduSink +agent1.sinks.sink1.masterAddresses = localhost +agent1.sinks.sink1.tableName = stats +agent1.sinks.sink1.channel = channel1 +agent1.sinks.sink1.batchSize = 50 +agent1.sinks.sink1.producer = org.apache.kudu.flume.sink.SimpleKuduEventProducer +</code></pre> + +<p>We define a source called <code>source1</code> which simply executes a <code>vmstat</code> command to continuously generate +virtual memory statistics for the machine and queue events into an in-memory <code>channel1</code> channel, +which in turn is used for writing these events to a Kudu table called <code>stats</code>. We are using +<code>org.apache.kudu.flume.sink.SimpleKuduEventProducer</code> as the producer. <code>SimpleKuduEventProducer</code> is +the built-in and default producer, but it’s implemented as a showcase for how to write Flume +events into Kudu tables. For any serious functionality we’d have to write a custom producer. We +need to make this producer and the <code>KuduSink</code> class available to Flume. We can do that by simply +copying the <code>kudu-flume-sink-<VERSION>.jar</code> jar file from the Kudu distribution to the +<code>$FLUME_HOME/plugins.d/kudu-sink/lib</code> directory in the Flume installation. The jar file contains +<code>KuduSink</code> and all of its dependencies (including Kudu java client classes).</p> + +<p>At a minimum, the Kudu Flume Sink needs to know where the Kudu masters are +(<code>agent1.sinks.sink1.masterAddresses = localhost</code>) and which Kudu table should be used for writing +Flume events to (<code>agent1.sinks.sink1.tableName = stats</code>). The Kudu Flume Sink doesn’t create this +table, it has to be created before the Kudu Flume Sink is started.</p> + +<p>You may also notice the <code>batchSize</code> parameter. Batch size is used for batching up to that many +Flume events and flushing the entire batch in one shot. Tuning batchSize properly can have a huge +impact on ingest performance of the Kudu cluster.</p> + +<p>Here is a complete list of KuduSink parameters:</p> + +<table> + <thead> + <tr> + <th>Parameter Name</th> + <th>Default</th> + <th>Description</th> + </tr> + </thead> + <tbody> + <tr> + <td>masterAddresses</td> + <td>N/A</td> + <td>Comma-separated list of “host:port” pairs of the masters (port optional)</td> + </tr> + <tr> + <td>tableName</td> + <td>N/A</td> + <td>The name of the table in Kudu to write to</td> + </tr> + <tr> + <td>producer</td> + <td>org.apache.kudu.flume.sink.SimpleKuduEventProducer</td> + <td>The fully qualified class name of the Kudu event producer the sink should use</td> + </tr> + <tr> + <td>batchSize</td> + <td>100</td> + <td>Maximum number of events the sink should take from the channel per transaction, if available</td> + </tr> + <tr> + <td>timeoutMillis</td> + <td>30000</td> + <td>Timeout period for Kudu operations, in milliseconds</td> + </tr> + <tr> + <td>ignoreDuplicateRows</td> + <td>true</td> + <td>Whether to ignore errors indicating that we attempted to insert duplicate rows into Kudu</td> + </tr> + </tbody> +</table> + +<p>Let’s take a look at the source code for the built-in producer class:</p> + +<pre><code class="language-java">public class SimpleKuduEventProducer implements KuduEventProducer { + private byte[] payload; + private KuduTable table; + private String payloadColumn; + + public SimpleKuduEventProducer(){ + } + + @Override + public void configure(Context context) { + payloadColumn = context.getString("payloadColumn","payload"); + } + + @Override + public void configure(ComponentConfiguration conf) { + } + + @Override + public void initialize(Event event, KuduTable table) { + this.payload = event.getBody(); + this.table = table; + } + + @Override + public List<Operation> getOperations() throws FlumeException { + try { + Insert insert = table.newInsert(); + PartialRow row = insert.getRow(); + row.addBinary(payloadColumn, payload); + + return Collections.singletonList((Operation) insert); + } catch (Exception e){ + throw new FlumeException("Failed to create Kudu Insert object!", e); + } + } + + @Override + public void close() { + } +} +</code></pre> + +<p><code>SimpleKuduEventProducer</code> implements the <code>org.apache.kudu.flume.sink.KuduEventProducer</code> interface, +which itself looks like this:</p> + +<pre><code class="language-java">public interface KuduEventProducer extends Configurable, ConfigurableComponent { + /** + * Initialize the event producer. + * @param event to be written to Kudu + * @param table the KuduTable object used for creating Kudu Operation objects + */ + void initialize(Event event, KuduTable table); + + /** + * Get the operations that should be written out to Kudu as a result of this + * event. This list is written to Kudu using the Kudu client API. + * @return List of {@link org.kududb.client.Operation} which + * are written as such to Kudu + */ + List<Operation> getOperations(); + + /* + * Clean up any state. This will be called when the sink is being stopped. + */ + void close(); +} +</code></pre> + +<p><code>public void configure(Context context)</code> is called when an instance of our producer is instantiated +by the KuduSink. SimpleKuduEventProducer’s implementation looks for a producer parameter named +<code>payloadColumn</code> and uses its value (“payload” if not overridden in Flume configuration file) as the +column which will hold the value of the Flume event payload. If you recall from above, we had +configured the KuduSink to listen for events generated from the <code>vmstat</code> command. Each output row +from that command will be stored as a new row containing a <code>payload</code> column in the <code>stats</code> table. +<code>SimpleKuduEventProducer</code> does not have any configuration parameters, but if it had any we would +define them by prefixing it with <code>producer.</code> (<code>agent1.sinks.sink1.producer.parameter1</code> for +example).</p> + +<p>The main producer logic resides in the <code>public List<Operation> getOperations()</code> method. In +SimpleKuduEventProducer’s implementation we simply insert the binary body of the Flume event into +the Kudu table. Here we call Kudu’s <code>newInsert()</code> to initiate an insert, but could have used +<code>Upsert</code> if updating an existing row was also an option, in fact there’s another producer +implementation available for doing just that: <code>SimpleKeyedKuduEventProducer</code>. Most probably you +will need to write your own custom producer in the real world, but you can base your implementation +on the built-in ones.</p> + +<p>In the future, we plan to add more flexible event producer implementations so that creation of a +custom event producer is not required to write data to Kudu. See +<a href="https://gerrit.cloudera.org/#/c/4034/";>here</a> for a work-in-progress generic event producer for +Avro-encoded Events.</p> + +<h2 id="conclusion">Conclusion</h2> + +<p>Kudu is a scalable data store which lets us ingest insane amounts of data per second. Apache Flume +helps us aggregate data from various sources, and the Kudu Flume Sink lets us easily store +the aggregated Flume events into Kudu. Together they enable us to create a data warehouse out of +disparate sources.</p> + +<p><em>Ara Abrahamian is a software engineer at Argyle Data building fraud detection systems using +sophisticated machine learning methods. Ara is the original author of the Flume Kudu Sink that +is included in the Kudu distribution. You can follow him on Twitter at +<a href="https://twitter.com/ara_e";>@ara_e</a>.</em></p> + + + + </div> + <div class="read-full"> + <a class="btn btn-info" href="/2016/08/31/intro-flume-kudu-sink.html">Read full post...</a> + </div> +</article> + + + +<!-- Articles --> +<article> + <header> <h1 class="entry-title"><a href="/2016/08/23/new-range-partitioning-features.html">New Range Partitioning Features in Kudu 0.10</a></h1> <p class="meta">Posted 23 Aug 2016 by Dan Burkert</p> </header> @@ -195,27 +509,6 @@ covers ongoing development and news in the Apache Kudu project.</p> -<!-- Articles --> -<article> - <header> - <h1 class="entry-title"><a href="/2016/07/26/weekly-update.html">Apache Kudu Weekly Update July 26, 2016</a></h1> - <p class="meta">Posted 26 Jul 2016 by Jean-Daniel Cryans</p> - </header> - <div class="entry-content"> - - <p>Welcome to the eighteenth edition of the Kudu Weekly Update. This weekly blog post -covers ongoing development and news in the Apache Kudu project.</p> - - - - </div> - <div class="read-full"> - <a class="btn btn-info" href="/2016/07/26/weekly-update.html">Read full post...</a> - </div> -</article> - - - <!-- Pagination links --> <nav> @@ -236,6 +529,8 @@ covers ongoing development and news in the Apache Kudu project.</p> <h3>Recent posts</h3> <ul> + <li> <a href="/2016/10/20/weekly-update.html">Apache Kudu Weekly Update October 20th, 2016</a> </li> + <li> <a href="/2016/10/11/weekly-update.html">Apache Kudu Weekly Update October 11th, 2016</a> </li> <li> <a href="/2016/09/26/strata-nyc-kudu-talks.html">Apache Kudu at Strata+Hadoop World NYC 2016</a> </li> @@ -264,8 +559,6 @@ covers ongoing development and news in the Apache Kudu project.</p> <li> <a href="/2016/07/01/apache-kudu-0-9-1-released.html">Apache Kudu (incubating) 0.9.1 released</a> </li> - <li> <a href="/2016/06/27/weekly-update.html">Apache Kudu (incubating) Weekly Update June 27, 2016</a> </li> - </ul> </div> </div> http://git-wip-us.apache.org/repos/asf/kudu-site/blob/9b3a1052/blog/page/3/index.html ---------------------------------------------------------------------- diff --git a/blog/page/3/index.html b/blog/page/3/index.html index d49613e..89eec1f 100644 --- a/blog/page/3/index.html +++ b/blog/page/3/index.html @@ -111,6 +111,27 @@ <!-- Articles --> <article> <header> + <h1 class="entry-title"><a href="/2016/07/26/weekly-update.html">Apache Kudu Weekly Update July 26, 2016</a></h1> + <p class="meta">Posted 26 Jul 2016 by Jean-Daniel Cryans</p> + </header> + <div class="entry-content"> + + <p>Welcome to the eighteenth edition of the Kudu Weekly Update. This weekly blog post +covers ongoing development and news in the Apache Kudu project.</p> + + + + </div> + <div class="read-full"> + <a class="btn btn-info" href="/2016/07/26/weekly-update.html">Read full post...</a> + </div> +</article> + + + +<!-- Articles --> +<article> + <header> <h1 class="entry-title"><a href="/2016/07/25/asf-graduation.html">The Apache Software Foundation Announces Apache® Kudu™ as a Top-Level Project</a></h1> <p class="meta">Posted 25 Jul 2016 by Jean-Daniel Cryans</p> </header> @@ -203,27 +224,6 @@ of 0.9.0 are encouraged to update to the new version at their earliest convenien -<!-- Articles --> -<article> - <header> - <h1 class="entry-title"><a href="/2016/06/27/weekly-update.html">Apache Kudu (incubating) Weekly Update June 27, 2016</a></h1> - <p class="meta">Posted 27 Jun 2016 by Todd Lipcon</p> - </header> - <div class="entry-content"> - - <p>Welcome to the fifteenth edition of the Kudu Weekly Update. This weekly blog post -covers ongoing development and news in the Apache Kudu (incubating) project.</p> - - - - </div> - <div class="read-full"> - <a class="btn btn-info" href="/2016/06/27/weekly-update.html">Read full post...</a> - </div> -</article> - - - <!-- Pagination links --> <nav> @@ -244,6 +244,8 @@ covers ongoing development and news in the Apache Kudu (incubating) project.</p> <h3>Recent posts</h3> <ul> + <li> <a href="/2016/10/20/weekly-update.html">Apache Kudu Weekly Update October 20th, 2016</a> </li> + <li> <a href="/2016/10/11/weekly-update.html">Apache Kudu Weekly Update October 11th, 2016</a> </li> <li> <a href="/2016/09/26/strata-nyc-kudu-talks.html">Apache Kudu at Strata+Hadoop World NYC 2016</a> </li> @@ -272,8 +274,6 @@ covers ongoing development and news in the Apache Kudu (incubating) project.</p> <li> <a href="/2016/07/01/apache-kudu-0-9-1-released.html">Apache Kudu (incubating) 0.9.1 released</a> </li> - <li> <a href="/2016/06/27/weekly-update.html">Apache Kudu (incubating) Weekly Update June 27, 2016</a> </li> - </ul> </div> </div> http://git-wip-us.apache.org/repos/asf/kudu-site/blob/9b3a1052/blog/page/4/index.html ---------------------------------------------------------------------- diff --git a/blog/page/4/index.html b/blog/page/4/index.html index fb3d8b6..adc6863 100644 --- a/blog/page/4/index.html +++ b/blog/page/4/index.html @@ -111,13 +111,34 @@ <!-- Articles --> <article> <header> + <h1 class="entry-title"><a href="/2016/06/27/weekly-update.html">Apache Kudu (incubating) Weekly Update June 27, 2016</a></h1> + <p class="meta">Posted 27 Jun 2016 by Todd Lipcon</p> + </header> + <div class="entry-content"> + + <p>Welcome to the fifteenth edition of the Kudu Weekly Update. This weekly blog post +covers ongoing development and news in the Apache Kudu (incubating) project.</p> + + + + </div> + <div class="read-full"> + <a class="btn btn-info" href="/2016/06/27/weekly-update.html">Read full post...</a> + </div> +</article> + + + +<!-- Articles --> +<article> + <header> <h1 class="entry-title"><a href="/2016/06/24/multi-master-1-0-0.html">Master fault tolerance in Kudu 1.0</a></h1> <p class="meta">Posted 24 Jun 2016 by Adar Dembo</p> </header> <div class="entry-content"> <p>This blog post describes how the 1.0 release of Apache Kudu (incubating) will -support fault tolerance for the Kudu master, finally eliminating Kuduâs last +support fault tolerance for the Kudu master, finally eliminating Kudu’s last single point of failure.</p> @@ -196,37 +217,6 @@ covers ongoing development and news in the Apache Kudu (incubating) project.</p> -<!-- Articles --> -<article> - <header> - <h1 class="entry-title"><a href="/2016/06/10/apache-kudu-0-9-0-released.html">Apache Kudu (incubating) 0.9.0 released</a></h1> - <p class="meta">Posted 10 Jun 2016 by Jean-Daniel Cryans</p> - </header> - <div class="entry-content"> - - <p>The Apache Kudu (incubating) team is happy to announce the release of Kudu -0.9.0!</p> - -<p>This latest version adds basic UPSERT functionality and an improved Apache Spark Data Source -that doesnât rely on the MapReduce I/O formats. It also improves Tablet Server -restart time as well as write performance under high load. Finally, Kudu now enforces -the specification of a partitioning scheme for new tables.</p> - -<ul> - <li>Read the detailed <a href="http://kudu.apache.org/releases/0.9.0/docs/release_notes.html";>Kudu 0.9.0 release notes</a></li> - <li>Download the <a href="http://kudu.apache.org/releases/0.9.0/";>Kudu 0.9.0 source release</a></li> -</ul> - - - - </div> - <div class="read-full"> - <a class="btn btn-info" href="/2016/06/10/apache-kudu-0-9-0-released.html">Read full post...</a> - </div> -</article> - - - <!-- Pagination links --> <nav> @@ -247,6 +237,8 @@ the specification of a partitioning scheme for new tables.</p> <h3>Recent posts</h3> <ul> + <li> <a href="/2016/10/20/weekly-update.html">Apache Kudu Weekly Update October 20th, 2016</a> </li> + <li> <a href="/2016/10/11/weekly-update.html">Apache Kudu Weekly Update October 11th, 2016</a> </li> <li> <a href="/2016/09/26/strata-nyc-kudu-talks.html">Apache Kudu at Strata+Hadoop World NYC 2016</a> </li> @@ -275,8 +267,6 @@ the specification of a partitioning scheme for new tables.</p> <li> <a href="/2016/07/01/apache-kudu-0-9-1-released.html">Apache Kudu (incubating) 0.9.1 released</a> </li> - <li> <a href="/2016/06/27/weekly-update.html">Apache Kudu (incubating) Weekly Update June 27, 2016</a> </li> - </ul> </div> </div> http://git-wip-us.apache.org/repos/asf/kudu-site/blob/9b3a1052/blog/page/5/index.html ---------------------------------------------------------------------- diff --git a/blog/page/5/index.html b/blog/page/5/index.html index b84c77c..efd90aa 100644 --- a/blog/page/5/index.html +++ b/blog/page/5/index.html @@ -111,6 +111,37 @@ <!-- Articles --> <article> <header> + <h1 class="entry-title"><a href="/2016/06/10/apache-kudu-0-9-0-released.html">Apache Kudu (incubating) 0.9.0 released</a></h1> + <p class="meta">Posted 10 Jun 2016 by Jean-Daniel Cryans</p> + </header> + <div class="entry-content"> + + <p>The Apache Kudu (incubating) team is happy to announce the release of Kudu +0.9.0!</p> + +<p>This latest version adds basic UPSERT functionality and an improved Apache Spark Data Source +that doesn’t rely on the MapReduce I/O formats. It also improves Tablet Server +restart time as well as write performance under high load. Finally, Kudu now enforces +the specification of a partitioning scheme for new tables.</p> + +<ul> + <li>Read the detailed <a href="http://kudu.apache.org/releases/0.9.0/docs/release_notes.html";>Kudu 0.9.0 release notes</a></li> + <li>Download the <a href="http://kudu.apache.org/releases/0.9.0/";>Kudu 0.9.0 source release</a></li> +</ul> + + + + </div> + <div class="read-full"> + <a class="btn btn-info" href="/2016/06/10/apache-kudu-0-9-0-released.html">Read full post...</a> + </div> +</article> + + + +<!-- Articles --> +<article> + <header> <h1 class="entry-title"><a href="/2016/06/06/weekly-update.html">Apache Kudu (incubating) Weekly Update June 6, 2016</a></h1> <p class="meta">Posted 06 Jun 2016 by Jean-Daniel Cryans</p> </header> @@ -194,27 +225,6 @@ covers ongoing development and news in the Apache Kudu (incubating) project.</p> -<!-- Articles --> -<article> - <header> - <h1 class="entry-title"><a href="/2016/05/16/weekly-update.html">Apache Kudu (incubating) Weekly Update May 16, 2016</a></h1> - <p class="meta">Posted 16 May 2016 by Todd Lipcon</p> - </header> - <div class="entry-content"> - - <p>Welcome to the ninth edition of the Kudu Weekly Update. This weekly blog post -covers ongoing development and news in the Apache Kudu (incubating) project.</p> - - - - </div> - <div class="read-full"> - <a class="btn btn-info" href="/2016/05/16/weekly-update.html">Read full post...</a> - </div> -</article> - - - <!-- Pagination links --> <nav> @@ -235,6 +245,8 @@ covers ongoing development and news in the Apache Kudu (incubating) project.</p> <h3>Recent posts</h3> <ul> + <li> <a href="/2016/10/20/weekly-update.html">Apache Kudu Weekly Update October 20th, 2016</a> </li> + <li> <a href="/2016/10/11/weekly-update.html">Apache Kudu Weekly Update October 11th, 2016</a> </li> <li> <a href="/2016/09/26/strata-nyc-kudu-talks.html">Apache Kudu at Strata+Hadoop World NYC 2016</a> </li> @@ -263,8 +275,6 @@ covers ongoing development and news in the Apache Kudu (incubating) project.</p> <li> <a href="/2016/07/01/apache-kudu-0-9-1-released.html">Apache Kudu (incubating) 0.9.1 released</a> </li> - <li> <a href="/2016/06/27/weekly-update.html">Apache Kudu (incubating) Weekly Update June 27, 2016</a> </li> - </ul> </div> </div> http://git-wip-us.apache.org/repos/asf/kudu-site/blob/9b3a1052/blog/page/6/index.html ---------------------------------------------------------------------- diff --git a/blog/page/6/index.html b/blog/page/6/index.html index 7b26d90..0129713 100644 --- a/blog/page/6/index.html +++ b/blog/page/6/index.html @@ -111,19 +111,19 @@ <!-- Articles --> <article> <header> - <h1 class="entry-title"><a href="/2016/05/09/weekly-update.html">Apache Kudu (incubating) Weekly Update May 9, 2016</a></h1> - <p class="meta">Posted 09 May 2016 by Jean-Daniel Cryans</p> + <h1 class="entry-title"><a href="/2016/05/16/weekly-update.html">Apache Kudu (incubating) Weekly Update May 16, 2016</a></h1> + <p class="meta">Posted 16 May 2016 by Todd Lipcon</p> </header> <div class="entry-content"> - <p>Welcome to the eighth edition of the Kudu Weekly Update. This weekly blog post + <p>Welcome to the ninth edition of the Kudu Weekly Update. This weekly blog post covers ongoing development and news in the Apache Kudu (incubating) project.</p> </div> <div class="read-full"> - <a class="btn btn-info" href="/2016/05/09/weekly-update.html">Read full post...</a> + <a class="btn btn-info" href="/2016/05/16/weekly-update.html">Read full post...</a> </div> </article> @@ -132,19 +132,19 @@ covers ongoing development and news in the Apache Kudu (incubating) project.</p> <!-- Articles --> <article> <header> - <h1 class="entry-title"><a href="/2016/05/03/weekly-update.html">Apache Kudu (incubating) Weekly Update May 3, 2016</a></h1> - <p class="meta">Posted 03 May 2016 by Todd Lipcon</p> + <h1 class="entry-title"><a href="/2016/05/09/weekly-update.html">Apache Kudu (incubating) Weekly Update May 9, 2016</a></h1> + <p class="meta">Posted 09 May 2016 by Jean-Daniel Cryans</p> </header> <div class="entry-content"> - <p>Welcome to the seventh edition of the Kudu Weekly Update. This weekly blog post + <p>Welcome to the eighth edition of the Kudu Weekly Update. This weekly blog post covers ongoing development and news in the Apache Kudu (incubating) project.</p> </div> <div class="read-full"> - <a class="btn btn-info" href="/2016/05/03/weekly-update.html">Read full post...</a> + <a class="btn btn-info" href="/2016/05/09/weekly-update.html">Read full post...</a> </div> </article> @@ -153,18 +153,19 @@ covers ongoing development and news in the Apache Kudu (incubating) project.</p> <!-- Articles --> <article> <header> - <h1 class="entry-title"><a href="/2016/04/26/ycsb.html">Benchmarking and Improving Kudu Insert Performance with YCSB</a></h1> - <p class="meta">Posted 26 Apr 2016 by Todd Lipcon</p> + <h1 class="entry-title"><a href="/2016/05/03/weekly-update.html">Apache Kudu (incubating) Weekly Update May 3, 2016</a></h1> + <p class="meta">Posted 03 May 2016 by Todd Lipcon</p> </header> <div class="entry-content"> - <p>Recently, I wanted to stress-test and benchmark some changes to the Kudu RPC server, and decided to use YCSB as a way to generate reasonable load. While running YCSB, I noticed interesting results, and what started as an unrelated testing exercise eventually yielded some new insights into Kuduâs behavior. These insights will motivate changes to default Kudu settings and code in upcoming versions. This post details the benchmark setup, analysis, and conclusions.</p> + <p>Welcome to the seventh edition of the Kudu Weekly Update. This weekly blog post +covers ongoing development and news in the Apache Kudu (incubating) project.</p> </div> <div class="read-full"> - <a class="btn btn-info" href="/2016/04/26/ycsb.html">Read full post...</a> + <a class="btn btn-info" href="/2016/05/03/weekly-update.html">Read full post...</a> </div> </article> @@ -173,19 +174,18 @@ covers ongoing development and news in the Apache Kudu (incubating) project.</p> <!-- Articles --> <article> <header> - <h1 class="entry-title"><a href="/2016/04/25/weekly-update.html">Apache Kudu (incubating) Weekly Update April 25, 2016</a></h1> - <p class="meta">Posted 25 Apr 2016 by Todd Lipcon</p> + <h1 class="entry-title"><a href="/2016/04/26/ycsb.html">Benchmarking and Improving Kudu Insert Performance with YCSB</a></h1> + <p class="meta">Posted 26 Apr 2016 by Todd Lipcon</p> </header> <div class="entry-content"> - <p>Welcome to the sixth edition of the Kudu Weekly Update. This weekly blog post -covers ongoing development and news in the Apache Kudu (incubating) project.</p> + <p>Recently, I wanted to stress-test and benchmark some changes to the Kudu RPC server, and decided to use YCSB as a way to generate reasonable load. While running YCSB, I noticed interesting results, and what started as an unrelated testing exercise eventually yielded some new insights into Kudu’s behavior. These insights will motivate changes to default Kudu settings and code in upcoming versions. This post details the benchmark setup, analysis, and conclusions.</p> </div> <div class="read-full"> - <a class="btn btn-info" href="/2016/04/25/weekly-update.html">Read full post...</a> + <a class="btn btn-info" href="/2016/04/26/ycsb.html">Read full post...</a> </div> </article> @@ -194,21 +194,19 @@ covers ongoing development and news in the Apache Kudu (incubating) project.</p> <!-- Articles --> <article> <header> - <h1 class="entry-title"><a href="/2016/04/19/kudu-0-8-0-predicate-improvements.html">Predicate Improvements in Kudu 0.8</a></h1> - <p class="meta">Posted 19 Apr 2016 by Dan Burkert</p> + <h1 class="entry-title"><a href="/2016/04/25/weekly-update.html">Apache Kudu (incubating) Weekly Update April 25, 2016</a></h1> + <p class="meta">Posted 25 Apr 2016 by Todd Lipcon</p> </header> <div class="entry-content"> - <p>The recently released Kudu version 0.8 ships with a host of new improvements to -scan predicates. Performance and usability have been improved, especially for -tables taking advantage of <a href="http://kudu.apache.org/docs/schema_design.html#data-distribution";>advanced partitioning -options</a>.</p> + <p>Welcome to the sixth edition of the Kudu Weekly Update. This weekly blog post +covers ongoing development and news in the Apache Kudu (incubating) project.</p> </div> <div class="read-full"> - <a class="btn btn-info" href="/2016/04/19/kudu-0-8-0-predicate-improvements.html">Read full post...</a> + <a class="btn btn-info" href="/2016/04/25/weekly-update.html">Read full post...</a> </div> </article> @@ -234,6 +232,8 @@ options</a>.</p> <h3>Recent posts</h3> <ul> + <li> <a href="/2016/10/20/weekly-update.html">Apache Kudu Weekly Update October 20th, 2016</a> </li> + <li> <a href="/2016/10/11/weekly-update.html">Apache Kudu Weekly Update October 11th, 2016</a> </li> <li> <a href="/2016/09/26/strata-nyc-kudu-talks.html">Apache Kudu at Strata+Hadoop World NYC 2016</a> </li> @@ -262,8 +262,6 @@ options</a>.</p> <li> <a href="/2016/07/01/apache-kudu-0-9-1-released.html">Apache Kudu (incubating) 0.9.1 released</a> </li> - <li> <a href="/2016/06/27/weekly-update.html">Apache Kudu (incubating) Weekly Update June 27, 2016</a> </li> - </ul> </div> </div> http://git-wip-us.apache.org/repos/asf/kudu-site/blob/9b3a1052/blog/page/7/index.html ---------------------------------------------------------------------- diff --git a/blog/page/7/index.html b/blog/page/7/index.html index b05f097..5e245f5 100644 --- a/blog/page/7/index.html +++ b/blog/page/7/index.html @@ -111,6 +111,29 @@ <!-- Articles --> <article> <header> + <h1 class="entry-title"><a href="/2016/04/19/kudu-0-8-0-predicate-improvements.html">Predicate Improvements in Kudu 0.8</a></h1> + <p class="meta">Posted 19 Apr 2016 by Dan Burkert</p> + </header> + <div class="entry-content"> + + <p>The recently released Kudu version 0.8 ships with a host of new improvements to +scan predicates. Performance and usability have been improved, especially for +tables taking advantage of <a href="http://kudu.apache.org/docs/schema_design.html#data-distribution";>advanced partitioning +options</a>.</p> + + + + </div> + <div class="read-full"> + <a class="btn btn-info" href="/2016/04/19/kudu-0-8-0-predicate-improvements.html">Read full post...</a> + </div> +</article> + + + +<!-- Articles --> +<article> + <header> <h1 class="entry-title"><a href="/2016/04/18/weekly-update.html">Apache Kudu (incubating) Weekly Update April 18, 2016</a></h1> <p class="meta">Posted 18 Apr 2016 by Todd Lipcon</p> </header> @@ -211,27 +234,6 @@ covers ongoing development and news in the Apache Kudu (incubating) project.</p> -<!-- Articles --> -<article> - <header> - <h1 class="entry-title"><a href="/2016/04/04/weekly-update.html">Apache Kudu (incubating) Weekly Update April 4, 2016</a></h1> - <p class="meta">Posted 04 Apr 2016 by Todd Lipcon</p> - </header> - <div class="entry-content"> - - <p>Welcome to the third edition of the Kudu Weekly Update. This weekly blog post -covers ongoing development and news in the Apache Kudu (incubating) project.</p> - - - - </div> - <div class="read-full"> - <a class="btn btn-info" href="/2016/04/04/weekly-update.html">Read full post...</a> - </div> -</article> - - - <!-- Pagination links --> <nav> @@ -252,6 +254,8 @@ covers ongoing development and news in the Apache Kudu (incubating) project.</p> <h3>Recent posts</h3> <ul> + <li> <a href="/2016/10/20/weekly-update.html">Apache Kudu Weekly Update October 20th, 2016</a> </li> + <li> <a href="/2016/10/11/weekly-update.html">Apache Kudu Weekly Update October 11th, 2016</a> </li> <li> <a href="/2016/09/26/strata-nyc-kudu-talks.html">Apache Kudu at Strata+Hadoop World NYC 2016</a> </li> @@ -280,8 +284,6 @@ covers ongoing development and news in the Apache Kudu (incubating) project.</p> <li> <a href="/2016/07/01/apache-kudu-0-9-1-released.html">Apache Kudu (incubating) 0.9.1 released</a> </li> - <li> <a href="/2016/06/27/weekly-update.html">Apache Kudu (incubating) Weekly Update June 27, 2016</a> </li> - </ul> </div> </div> http://git-wip-us.apache.org/repos/asf/kudu-site/blob/9b3a1052/blog/page/8/index.html ---------------------------------------------------------------------- diff --git a/blog/page/8/index.html b/blog/page/8/index.html index 4d26c3a..28a39fb 100644 --- a/blog/page/8/index.html +++ b/blog/page/8/index.html @@ -111,13 +111,34 @@ <!-- Articles --> <article> <header> + <h1 class="entry-title"><a href="/2016/04/04/weekly-update.html">Apache Kudu (incubating) Weekly Update April 4, 2016</a></h1> + <p class="meta">Posted 04 Apr 2016 by Todd Lipcon</p> + </header> + <div class="entry-content"> + + <p>Welcome to the third edition of the Kudu Weekly Update. This weekly blog post +covers ongoing development and news in the Apache Kudu (incubating) project.</p> + + + + </div> + <div class="read-full"> + <a class="btn btn-info" href="/2016/04/04/weekly-update.html">Read full post...</a> + </div> +</article> + + + +<!-- Articles --> +<article> + <header> <h1 class="entry-title"><a href="/2016/03/28/weekly-update.html">Apache Kudu (incubating) Weekly Update March 28, 2016</a></h1> <p class="meta">Posted 28 Mar 2016 by Todd Lipcon</p> </header> <div class="entry-content"> - <p>Welcome to the second edition of the Kudu Weekly Update. As with last weekâs -inaugural post, weâll cover ongoing development and news in the Apache Kudu + <p>Welcome to the second edition of the Kudu Weekly Update. As with last week’s +inaugural post, we’ll cover ongoing development and news in the Apache Kudu project on a weekly basis.</p> @@ -138,13 +159,13 @@ project on a weekly basis.</p> </header> <div class="entry-content"> - <p>Kudu is a fast-moving young open source project, and weâve heard from a few -members of the community that it can be difficult to keep track of whatâs + <p>Kudu is a fast-moving young open source project, and we’ve heard from a few +members of the community that it can be difficult to keep track of what’s going on day-to-day. A typical month comprises 80-100 individual patches committed and hundreds of code review and discussion emails. So, inspired by similar weekly newsletters like -<a href="http://llvmweekly.org/";>LLVM Weekly</a> and <a href="http://lwn.net/Kernel/";>LWNâs weekly kernel coverage</a> -weâre going to experiment with our own weekly newsletter covering +<a href="http://llvmweekly.org/";>LLVM Weekly</a> and <a href="http://lwn.net/Kernel/";>LWN’s weekly kernel coverage</a> +we’re going to experiment with our own weekly newsletter covering recent development and Kudu-related news.</p> @@ -223,6 +244,8 @@ part of the ASF Incubator, version 0.7.0!</p> <h3>Recent posts</h3> <ul> + <li> <a href="/2016/10/20/weekly-update.html">Apache Kudu Weekly Update October 20th, 2016</a> </li> + <li> <a href="/2016/10/11/weekly-update.html">Apache Kudu Weekly Update October 11th, 2016</a> </li> <li> <a href="/2016/09/26/strata-nyc-kudu-talks.html">Apache Kudu at Strata+Hadoop World NYC 2016</a> </li> @@ -251,8 +274,6 @@ part of the ASF Incubator, version 0.7.0!</p> <li> <a href="/2016/07/01/apache-kudu-0-9-1-released.html">Apache Kudu (incubating) 0.9.1 released</a> </li> - <li> <a href="/2016/06/27/weekly-update.html">Apache Kudu (incubating) Weekly Update June 27, 2016</a> </li> - </ul> </div> </div> http://git-wip-us.apache.org/repos/asf/kudu-site/blob/9b3a1052/feed.xml ---------------------------------------------------------------------- diff --git a/feed.xml b/feed.xml index fa33deb..505d151 100644 --- a/feed.xml +++ b/feed.xml @@ -1,4 +1,92 @@ -<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom";><generator uri="http://jekyllrb.com"; version="2.5.3">Jekyll</generator><link href="/feed.xml" rel="self" type="application/atom+xml" /><link href="/" rel="alternate" type="text/html" /><updated>2016-10-11T15:00:02-07:00</updated><id>/</id><entry><title>Apache Kudu Weekly Update October 11th, 2016</title><link href="/2016/10/11/weekly-update.html" rel="alternate" type="text/html" title="Apache Kudu Weekly Update October 11th, 2016" /><published>2016-10-11T00:00:00-07:00</published><updated>2016-10-11T00:00:00-07:00</updated><id>/2016/10/11/weekly-update</id><content type="html" xml:base="/2016/10/11/weekly-update.html"><p>Welcome to the twenty-first edition of the Kudu Weekly Update. Astute +<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom";><generator uri="http://jekyllrb.com"; version="2.5.3">Jekyll</generator><link href="/feed.xml" rel="self" type="application/atom+xml" /><link href="/" rel="alternate" type="text/html" /><updated>2016-10-20T17:57:46-07:00</updated><id>/</id><entry><title>Apache Kudu Weekly Update October 20th, 2016</title><link href="/2016/10/20/weekly-update.html" rel="alternate" type="text/html" title="Apache Kudu Weekly Update October 20th, 2016" /><published>2016-10-20T00:00:00-07:00</published><updated>2016-10-20T00:00:00-07:00</updated><id>/2016/10/20/weekly-update</id><content type="html" xml:base="/2016/10/20/weekly-update.html"><p>Welcome to the twenty-second edition of the Kudu Weekly Update. This weekly blog post +covers ongoing development and news in the Apache Kudu project.</p> + +<!--more--> + +<h2 id="project-news">Project news</h2> + +<ul> + <li> + <p>Kudu 1.0.1 was <a href="http://mail-archives.apache.org/mod_mbox/kudu-user/201610.mbox/%3CCALo2W-UgTa%2BX15_q_9FQpRUPWN53eyqFS10C5MXK1KpsFgqcyQ%40mail.gmail.com%3E">released</a> +on October 11th. This is a bug fix release which fixes several bugs found +in 1.0.0. See the <a href="http://kudu.apache.org/releases/1.0.1/docs/release_notes.html">Kudu 1.0.1 release notes</a> +for more details.</p> + </li> + <li> + <p>Todd Lipcon has proposed a <a href="https://lists.apache.org/thread.html/4c94d313e28381bb107682ffaf43adfd38bd7fb3b03c98e3c86c52e2@%3Cdev.kudu.apache.org%3E">release plan</a> +for the next few months. The proposal is to have a 1.1 release in mid-November and +a 1.2 release in mid-January. These would be time-based releases rather than +gated on any particular feature scope; however, itâs anticipated that several +new features and improvements will be ready in time for these releases.</p> + </li> + <li> + <p>Happy fourth birthday to the Kudu project! The initial commit was made +on October 11th, 2012! Since then weâve had 4888 more commits by 60 +authors!</p> + </li> +</ul> + +<h2 id="development-discussions-and-code-in-progress">Development discussions and code in progress</h2> + +<ul> + <li>As mentioned last week, a lot of contributors have been collaborating on +design documents for upcoming work. Hereâs the complete list of in-flight +documents, along with the primary authors of these docs: + <ul> + <li><a href="https://docs.google.com/document/d/1cPNDTpVkIUo676RlszpTF1gHZ8l0TdbB7zFBAuOuYUw/edit#heading=h.gsibhnd5dyem">Security features</a> (Todd Lipcon)</li> + <li><a href="https://goo.gl/wP5BJb">Improved disk-failure handling</a> (Dinesh Bhat)</li> + <li><a href="https://s.apache.org/7K48">Tools for manual recovery from corruption</a> (Mike Percy and Dinesh Bhat)</li> + <li><a href="https://s.apache.org/uOOt">Addressing issues seen with the LogBlockManager</a> (Adar Dembo)</li> + <li><a href="https://s.apache.org/7VCo">Providing proper snapshot/serializable consistency</a> (David Alves)</li> + <li><a href="https://s.apache.org/ARUP">Improving re-replication of under-replicated tablets</a> (Mike Percy)</li> + <li><a href="https://docs.google.com/document/d/1066W63e2YUTNnecmfRwgAHghBPnL1Pte_gJYAaZ_Bjo/edit">Avoiding Raft election storms</a> (Todd Lipcon)</li> + <li><a href="https://s.apache.org/kudu-backup-scope">Backup and bulk load</a> (Dan Burkert)</li> + <li><a href="https://s.apache.org/SM6V">Improving diagnosability of client errors</a> (Alexey Serbin)</li> + </ul> + + <p>In many cases, work is now progressing on implementation of these ideas, +but these are considered living documents. Itâs not too late to add your +comments or volunteer to help out.</p> + </li> + <li> + <p>JD Cryans has been working on cleaning up the Java client. Several complex pieces +of code were completely removed, and other parts were refactored into new +standalone classes for better modularity. Along the way, JD also +<a href="http://gerrit.cloudera.org:8080/4706">reduced lock contention</a> on a frequently-accessed +data structure.</p> + </li> + <li> + <p>Todd Lipcon implemented and committed Raft âpre-electionsâ as described in the +[election storm mitigation design document]((https://docs.google.com/document/d/1066W63e2YUTNnecmfRwgAHghBPnL1Pte_gJYAaZ_Bjo/edit). +Initial experiments, detailed in the document, indicate that this will substantially +improve leader stability on clusters with overloaded disks and lots of tablets.</p> + + <p>Following this patch, Todd worked on some cleanup and refactor of the Consensus +implementation, removing a bunch of dead code and splitting some classes up +into smaller pieces. This is preparing for some improvements in locking +granularity also described in the same document.</p> + </li> + <li> + <p>Dan Burkert and Todd Lipcon have started submitting patches to integrate Kerberos +authentication with Kuduâs RPC system. Dan posted a +<a href="https://gerrit.cloudera.org/#/c/4752/">patch</a> which adds âMiniKDCâ, some test +infrastructure for starting and stopping a standalone Kerberos service in +the context of a test. Todd worked on adding +<a href="https://gerrit.cloudera.org/#/c/4763/">support for Kerberos authentication</a> +during RPC negotiation.</p> + + <p>These patches are just the beginning of the security work, but form an important +base to build on top of. The design uses Kerberos both as a mechanism to authenticate +clients as well as a way to mutually authenticate tablet servers with the master.</p> + </li> +</ul> + +<p>Want to learn more about a specific topic from this blog post? Shoot an email to the +<a href="&#109;&#097;&#105;&#108;&#116;&#111;:&#117;&#115;&#101;&#114;&#064;&#107;&#117;&#100;&#117;&#046;&#097;&#112;&#097;&#099;&#104;&#101;&#046;&#111;&#114;&#103;">kudu-user mailing list</a> or +tweet at <a href="https://twitter.com/ApacheKudu">@ApacheKudu</a>. Similarly, if youâre +aware of some Kudu news we missed, let us know so we can cover it in +a future post.</p></content><author><name>Todd Lipcon</name></author><summary>Welcome to the twenty-second edition of the Kudu Weekly Update. This weekly blog post +covers ongoing development and news in the Apache Kudu project.</summary></entry><entry><title>Apache Kudu Weekly Update October 11th, 2016</title><link href="/2016/10/11/weekly-update.html" rel="alternate" type="text/html" title="Apache Kudu Weekly Update October 11th, 2016" /><published>2016-10-11T00:00:00-07:00</published><updated>2016-10-11T00:00:00-07:00</updated><id>/2016/10/11/weekly-update</id><content type="html" xml:base="/2016/10/11/weekly-update.html"><p>Welcome to the twenty-first edition of the Kudu Weekly Update. Astute readers will notice that the weekly blog posts have been not-so-weekly of late â in fact, it has been nearly two months since the previous post as I and others have focused on releases, conferences, etc.</p> @@ -158,11 +246,11 @@ tweet at <a href="https://twitter.com/ApacheKudu">@ApacheKudu< aware of some Kudu news we missed, let us know so we can cover it in a future post.</p></content><author><name>Todd Lipcon</name></author><summary>Welcome to the twenty-first edition of the Kudu Weekly Update. Astute readers will notice that the weekly blog posts have been not-so-weekly -of late â in fact, it has been nearly two months since the previous post +of late &#8211; in fact, it has been nearly two months since the previous post as I and others have focused on releases, conferences, etc. So, rather than covering just this past week, this post will cover highlights -of the progress since the 1.0 release in mid-September. If youâre interested +of the progress since the 1.0 release in mid-September. If you&#8217;re interested in learning about progress prior to that release, check the release notes.</summary></entry><entry><title>Apache Kudu at Strata+Hadoop World NYC 2016</title><link href="/2016/09/26/strata-nyc-kudu-talks.html" rel="alternate" type="text/html" title="Apache Kudu at Strata+Hadoop World NYC 2016" /><published>2016-09-26T00:00:00-07:00</published><updated>2016-09-26T00:00:00-07:00</updated><id>/2016/09/26/strata-nyc-kudu-talks</id><content type="html" xml:base="/2016/09/26/strata-nyc-kudu-talks.html"><p>This week in New York, OâReilly and Cloudera will be hosting Strata+Hadoop World 2016. If youâre interested in Kudu, there will be several opportunities to @@ -218,8 +306,8 @@ featuring Apache Kudu at the Cloudera and ZoomData vendor booths.</p> <p>If youâre not attending the conference, but still based in NYC, all hope is not lost. Michael Crutcher from Cloudera will be presenting an introduction to Apache Kudu at the <a href="http://www.meetup.com/mysqlnyc/events/233599664/">SQL NYC Meetup</a>. -Be sure to RSVP as spots are filling up fast.</p></content><author><name>Todd Lipcon</name></author><summary>This week in New York, OâReilly and Cloudera will be hosting Strata+Hadoop World -2016. If youâre interested in Kudu, there will be several opportunities to +Be sure to RSVP as spots are filling up fast.</p></content><author><name>Todd Lipcon</name></author><summary>This week in New York, O&#8217;Reilly and Cloudera will be hosting Strata+Hadoop World +2016. If you&#8217;re interested in Kudu, there will be several opportunities to learn more, both from the open source development team as well as some companies who are already adopting Kudu for their use cases.</summary></entry><entry><title>Apache Kudu 1.0.0 released</title><link href="/2016/09/20/apache-kudu-1-0-0-released.html" rel="alternate" type="text/html" title="Apache Kudu 1.0.0 released" /><published>2016-09-20T00:00:00-07:00</published><updated>2016-09-20T00:00:00-07:00</updated><id>/2016/09/20/apache-kudu-1-0-0-released</id><content type="html" xml:base="/2016/09/20/apache-kudu-1-0-0-released.html"><p>The Apache Kudu team is happy to announce the release of Kudu 1.0.0!</p> @@ -694,12 +782,12 @@ disparate sources.</p> <p><em>Ara Abrahamian is a software engineer at Argyle Data building fraud detection systems using sophisticated machine learning methods. Ara is the original author of the Flume Kudu Sink that is included in the Kudu distribution. You can follow him on Twitter at -<a href="https://twitter.com/ara_e">@ara_e</a>.</em></p></content><author><name>Ara Abrahamian</name></author><summary>This post discusses the Kudu Flume Sink. First, Iâll give some background on why we considered +<a href="https://twitter.com/ara_e">@ara_e</a>.</em></p></content><author><name>Ara Abrahamian</name></author><summary>This post discusses the Kudu Flume Sink. First, I&#8217;ll give some background on why we considered using Kudu, what Flume does for us, and how Flume fits with Kudu in our project. Why Kudu -Traditionally in the Hadoop ecosystem weâve dealt with various batch processing technologies such +Traditionally in the Hadoop ecosystem we&#8217;ve dealt with various batch processing technologies such as MapReduce and the many libraries and tools built on top of it in various languages (Apache Pig, Apache Hive, Apache Oozie and many others). The main problem with this approach is that it needs to process the whole data set in batches, again and again, as soon as new data gets added. Things get @@ -739,14 +827,14 @@ And a Kudu-based near real-time approach is: flexible and expressive, thanks to SQL support via Apache Impala (incubating) a table-oriented, mutable data store that feels like a traditional relational database - very easy to program, you can even pretend itâs good old MySQL + very easy to program, you can even pretend it&#8217;s good old MySQL low-latency and relatively high throughput, both for ingest and query -At Argyle Data, weâre dealing with complex fraud detection scenarios. We need to ingest massive +At Argyle Data, we&#8217;re dealing with complex fraud detection scenarios. We need to ingest massive amounts of data, run machine learning algorithms and generate reports. When we created our current architecture two years ago we decided to opt for a database as the backbone of our system. That -database is Apache Accumulo. Itâs a key-value based database which runs on top of Hadoop HDFS, +database is Apache Accumulo. It&#8217;s a key-value based database which runs on top of Hadoop HDFS, quite similar to HBase but with some important improvements such as cell level security and ease of deployment and management. To enable querying of this data for quite complex reporting and analytics, we used Presto, a distributed query engine with a pluggable architecture open-sourced @@ -759,12 +847,12 @@ architecture has served us well, but there were a few problems: we need to support ad-hoc queries, plus long-term data warehouse functionality -So, weâve started gradually moving the core machine-learning pipeline to a streaming based +So, we&#8217;ve started gradually moving the core machine-learning pipeline to a streaming based solution. This way we can ingest and process larger data-sets faster in the real-time. But then how would we take care of ad-hoc queries and long-term persistence? This is where Kudu comes in. While the machine learning pipeline ingests and processes real-time data, we store a copy of the same ingested data in Kudu for long-term access and ad-hoc queries. Kudu is our data warehouse. By -using Kudu and Impala, we can retire our in-house Presto connector and rely on Impalaâs +using Kudu and Impala, we can retire our in-house Presto connector and rely on Impala&#8217;s super-fast query engine. But how would we make sure data is reliably ingested into the streaming pipeline and the @@ -772,10 +860,10 @@ Kudu-based data warehouse? This is where Apache Flume comes in. Why Flume -According to their website âFlume is a distributed, reliable, and +According to their website &#8220;Flume is a distributed, reliable, and available service for efficiently collecting, aggregating, and moving large amounts of log data. It has a simple and flexible architecture based on streaming data flows. It is robust and fault -tolerant with tunable reliability mechanisms and many failover and recovery mechanisms.â As you +tolerant with tunable reliability mechanisms and many failover and recovery mechanisms.&#8221; As you can see, nowhere is Hadoop mentioned but Flume is typically used for ingesting data to Hadoop clusters. @@ -793,7 +881,7 @@ File-based channels are also provided. As for the sources, Avro, JMS, Thrift, sp source are some of the built-in ones. Flume also ships with many sinks, including sinks for writing data to HDFS, HBase, Hive, Kafka, as well as to other Flume agents. -In the rest of this post Iâll go over the Kudu Flume sink and show you how to configure Flume to +In the rest of this post I&#8217;ll go over the Kudu Flume sink and show you how to configure Flume to write ingested data to a Kudu table. The sink has been part of the Kudu distribution since the 0.8 release and the source code can be found here. @@ -825,8 +913,8 @@ We define a source called source1 which simply executes a vmstat command to cont virtual memory statistics for the machine and queue events into an in-memory channel1 channel, which in turn is used for writing these events to a Kudu table called stats. We are using org.apache.kudu.flume.sink.SimpleKuduEventProducer as the producer. SimpleKuduEventProducer is -the built-in and default producer, but itâs implemented as a showcase for how to write Flume -events into Kudu tables. For any serious functionality weâd have to write a custom producer. We +the built-in and default producer, but it&#8217;s implemented as a showcase for how to write Flume +events into Kudu tables. For any serious functionality we&#8217;d have to write a custom producer. We need to make this producer and the KuduSink class available to Flume. We can do that by simply copying the kudu-flume-sink-&lt;VERSION&gt;.jar jar file from the Kudu distribution to the $FLUME_HOME/plugins.d/kudu-sink/lib directory in the Flume installation. The jar file contains @@ -834,7 +922,7 @@ KuduSink and all of its dependencies (including Kudu java client classes). At a minimum, the Kudu Flume Sink needs to know where the Kudu masters are (agent1.sinks.sink1.masterAddresses = localhost) and which Kudu table should be used for writing -Flume events to (agent1.sinks.sink1.tableName = stats). The Kudu Flume Sink doesnât create this +Flume events to (agent1.sinks.sink1.tableName = stats). The Kudu Flume Sink doesn&#8217;t create this table, it has to be created before the Kudu Flume Sink is started. You may also notice the batchSize parameter. Batch size is used for batching up to that many @@ -855,7 +943,7 @@ Here is a complete list of KuduSink parameters: masterAddresses N/A - Comma-separated list of âhost:portâ pairs of the masters (port optional) + Comma-separated list of &#8220;host:port&#8221; pairs of the masters (port optional) tableName @@ -885,7 +973,7 @@ Here is a complete list of KuduSink parameters: -Letâs take a look at the source code for the built-in producer class: +Let&#8217;s take a look at the source code for the built-in producer class: public class SimpleKuduEventProducer implements KuduEventProducer { private byte[] payload; @@ -956,8 +1044,8 @@ public interface KuduEventProducer extends Configurable, ConfigurableComponent { public void configure(Context context) is called when an instance of our producer is instantiated -by the KuduSink. SimpleKuduEventProducerâs implementation looks for a producer parameter named -payloadColumn and uses its value (âpayloadâ if not overridden in Flume configuration file) as the +by the KuduSink. SimpleKuduEventProducer&#8217;s implementation looks for a producer parameter named +payloadColumn and uses its value (&#8220;payload&#8221; if not overridden in Flume configuration file) as the column which will hold the value of the Flume event payload. If you recall from above, we had configured the KuduSink to listen for events generated from the vmstat command. Each output row from that command will be stored as a new row containing a payload column in the stats table. @@ -966,9 +1054,9 @@ define them by prefixing it with producer. (agent1.sinks.sink1.producer.paramete example). The main producer logic resides in the public List&lt;Operation&gt; getOperations() method. In -SimpleKuduEventProducerâs implementation we simply insert the binary body of the Flume event into -the Kudu table. Here we call Kuduâs newInsert() to initiate an insert, but could have used -Upsert if updating an existing row was also an option, in fact thereâs another producer +SimpleKuduEventProducer&#8217;s implementation we simply insert the binary body of the Flume event into +the Kudu table. Here we call Kudu&#8217;s newInsert() to initiate an insert, but could have used +Upsert if updating an existing row was also an option, in fact there&#8217;s another producer implementation available for doing just that: SimpleKeyedKuduEventProducer. Most probably you will need to write your own custom producer in the real world, but you can base your implementation on the built-in ones. @@ -1301,72 +1389,4 @@ Apache Hadoop ecosystem, and goals for the upcoming 1.0 release.</li> tweet at <a href="https://twitter.com/ApacheKudu">@ApacheKudu</a>. Similarly, if youâre aware of some Kudu news we missed, let us know so we can cover it in a future post.</p></content><author><name>Todd Lipcon</name></author><summary>Welcome to the nineteenth edition of the Kudu Weekly Update. This weekly blog post -covers ongoing development and news in the Apache Kudu project.</summary></entry><entry><title>Apache Kudu Weekly Update July 26, 2016</title><link href="/2016/07/26/weekly-update.html" rel="alternate" type="text/html" title="Apache Kudu Weekly Update July 26, 2016" /><published>2016-07-26T00:00:00-07:00</published><updated>2016-07-26T00:00:00-07:00</updated><id>/2016/07/26/weekly-update</id><content type="html" xml:base="/2016/07/26/weekly-update.html"><p>Welcome to the eighteenth edition of the Kudu Weekly Update. This weekly blog post -covers ongoing development and news in the Apache Kudu project.</p> - -<!--more--> - -<h2 id="project-news">Project news</h2> - -<ul> - <li>Kudu has graduated from the Apache Incubator and is now a Top-Level Project! All the details -are in this <a href="http://kudu.apache.org/2016/07/25/asf-graduation.html">blog post</a>. -Mike Percy and Todd Lipcon made a few updates to the website to reflect the projectâs -new name and status.</li> -</ul> - -<h2 id="development-discussions-and-code-in-progress">Development discussions and code in progress</h2> - -<ul> - <li> - <p>Dan Burkert contributed a few patches that repackage the Java client under <code>org.apache.kudu</code> -in place of <code>org.kududb</code>. This was done in a <strong>backward-incompatible</strong> way, meaning that import -statements will have to be modified in existing Java code to compile against a newer Kudu JAR -version (from 0.10.0 onward). This stems from <a href="http://mail-archives.apache.org/mod_mbox/kudu-dev/201605.mbox/%3ccagptdncjohqbgjzxafxjqdqmbb4sl495p5v_bjrxk_nagwb...@mail.gmail.com%3E">a discussion</a> -initiated in May. It wonât have an impact on C++ or Python users, and it isnât affecting wire -compatibility.</p> - </li> - <li> - <p>Still on the Java-side, J-D Cryans pushed <a href="https://gerrit.cloudera.org/#/c/3055/">a patch</a> -that completely changes how Exceptions are managed. Before this change, users had to introspect -generic Exception objects, making it a guessing game and discouraging good error handling. -Now, the synchronous clientâs methods throw <code>KuduException</code> which packages a <code>Status</code> object -that can be interrogated. This is very similar to how the C++ API works.</p> - - <p>Existing code that uses the new Kudu JAR should still compile since this change replaces generic -<code>Exception</code> with a more specific <code>KuduException</code>. Error handling done by string-matching the -exception messages should now use the provided <code>Status</code> object.</p> - </li> - <li> - <p>Alexey Serbinâs <a href="https://gerrit.cloudera.org/#/c/3619/">patch</a> that adds Doxygen-based -documentation was pushed and the new API documentation for C++ developers will be available -with the next release.</p> - </li> - <li> - <p>Todd has made many improvements to the <code>ksck</code> tool over the last week. Building upon Will -Berkeleyâs <a href="https://gerrit.cloudera.org/#/c/3632/">WIP patch for KUDU-1516</a>, <code>ksck</code> can -now detect more problematic situations like if a tablet doesnât have a majority of replicas on -live tablet servers, or if those replicas arenât in a good state. -<code>ksck</code> is also <a href="https://gerrit.cloudera.org/#/c/3705/">now faster</a> when run against a large -cluster with a lot of tablets, among other improvements.</p> - </li> - <li> - <p>As mentioned last week, Dan has been working on <a href="https://gerrit.cloudera.org/#/c/3648/">adding add/remove range partition support</a> -in the C++ client and in the master. The patch has been through many rounds of review and -testing and itâs getting close to completion. Meanwhile, J-D started looking at adding support -for this functionality in the <a href="https://gerrit.cloudera.org/#/c/3731/">Java client</a>.</p> - </li> - <li> - <p>Adar Dembo is also hard at work on the master. The <a href="https://gerrit.cloudera.org/#/c/3609/">series</a> -<a href="https://gerrit.cloudera.org/#/c/3610/">of</a> <a href="https://gerrit.cloudera.org/#/c/3611/">patches</a> to -have the tablet servers heartbeat to all the masters that he published earlier this month is -getting near the finish line.</p> - </li> -</ul> - -<p>Want to learn more about a specific topic from this blog post? Shoot an email to the -<a href="&#109;&#097;&#105;&#108;&#116;&#111;:&#117;&#115;&#101;&#114;&#064;&#107;&#117;&#100;&#117;&#046;&#105;&#110;&#099;&#117;&#098;&#097;&#116;&#111;&#114;&#046;&#097;&#112;&#097;&#099;&#104;&#101;&#046;&#111;&#114;&#103;">kudu-user mailing list</a> or -tweet at <a href="https://twitter.com/ApacheKudu">@ApacheKudu</a>. Similarly, if youâre -aware of some Kudu news we missed, let us know so we can cover it in -a future post.</p></content><author><name>Jean-Daniel Cryans</name></author><summary>Welcome to the eighteenth edition of the Kudu Weekly Update. This weekly blog post covers ongoing development and news in the Apache Kudu project.</summary></entry></feed>
