/*
 * The Alluxio Open Foundation licenses this work under the Apache License, version 2.0
 * (the "License"). You may not use this work except in compliance with the License, which is
 * available at www.apache.org/licenses/LICENSE-2.0
 *
 * This software is distributed on an "AS IS" basis, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND,
 * either express or implied, as more fully set forth in the License.
 *
 * See the NOTICE file distributed with this work for information regarding copyright ownership.
 */

/**
 * Worker process and utils for working with the worker remotely.
 *
 * Main entry point for the worker is {@link alluxio.worker.AlluxioWorker#main(String[])}
 * which gets started by the alluxio start scripts. The {@link alluxio.worker.WorkerProcess}
 * spins up the different RPC services (thrift, data) which are mostly wrappers around
 * {@link alluxio.worker.block.BlockWorker}.
 *
 * <h1>Services</h1>
 *
 * <h2>Thrift</h2>
 *
 * The thrift service is mostly responsible for metadata operations (with a few operations that
 * effect the worker's cached memory).
 *
 * <h3>Cache Block</h3>
 *
 * Move's user generated blocks to the alluxio data directory. This operation expects that the
 * caller is a local (to the node) caller, and that the input are under the user directories.
 *
 * Implementation can be found at {@link alluxio.worker.block.BlockWorker#commitBlock(long, long)}
 *
 * <h3>Lock / Unlock</h3>
 *
 * Alluxio supports caching blocks to local disk (client side). When this happens, a lock is given
 * to the client to protect it from the remote block changing.
 *
 * Implementation can be found at {@link alluxio.worker.block.BlockWorker#lockBlock(long, long)} and
 * {@link alluxio.worker.block.BlockWorker#unlockBlock(long, long)}.
 *
 * <h2>Data</h2>
 *
 * This service is the main interaction between users and reading blocks. Currently this service
 * only supports reading blocks (writing is to local disk).
 *
 * There are two different implementations of this layer:
 * {@link alluxio.worker.netty.NettyDataServer} and {@link alluxio.worker.nio.NIODataServer}; netty
 * is the default. To support both, a {@link alluxio.worker.DataServer} interface is used that just
 * defines how to start/stop, and get port details; to start, object init is used.
 *
 * The current read protocol is defined in {@link alluxio.worker.DataServerMessage}. This has two
 * different types: read {@link alluxio.worker.DataServerMessage#createBlockRequestMessage} and
 * write {@link alluxio.worker.DataServerMessage#createBlockResponseMessage}. Side note, the netty
 * implementation does not use this class, but has defined two classes for the read and write case:
 * {@link alluxio.network.protocol.RPCBlockReadRequest},
 * {@link alluxio.network.protocol.RPCBlockReadResponse}; theses classes are network compatible.
 */

package alluxio.worker;

@@ -662,18 +662,8 @@
 main
-(String%5B%5D)
 %7D%0A *
@@ -923,14 +923,18 @@
 %3Ch2%3E
-Thrift
+DataServer
 %3C/h2
@@ -947,16 +947,10 @@
 * Th
-e thrift
+is
  ser
@@ -961,1184 +961,599 @@
  is 
-mostly responsible for metadata operations (with a few op
+the main int
 era
+c
 tion
-s that%0A * effect the worker's cached memory).%0A *%0A * %3Ch3%3ECache Block%3C/h3%3E%0A *%0A * Move's user generated blocks to the alluxio data directory. This operation expects that the%0A * caller is a local (to the node) caller, and that the input are under the user directories.%0A *%0A * Implementation can be found at %7B@link alluxio.worker.block.BlockWorker#commitBlock(long, long)%7D%0A *%0A * %3Ch3%3ELock / Unlock%3C/h3%3E%0A *%0A * Alluxio supports caching blocks to local disk (client side). When this happens, a lock is given%0A * to the client to prot
+ between users and worker for reading and writing blocks.%0A * The %7B@link alluxio.worker.DataServer%7D interface defines how to start/stop, and get port details;%0A * to start, obj
 ect 
+in
 it 
-from the remote block changing.%0A *%0A * Implementation can be found at %7B@link alluxio.worker.block.BlockWorker#lockBlock(long, long)%7D and%0A * %7B@link alluxio.worker.block.BlockWorker#unlockBlock(long, long)%7D.%0A *%0A * %3Ch2%3EData%3C/h2%3E%0A *%0A * This service is the main interaction between users and reading blocks. Currently this service%0A * only supports reading blocks (writing is to local disk).%0A *%0A * There are two different implementations of this layer:%0A * %7B@link alluxio.worker.netty.NettyDataS
+is used. The implementation of this interface is in%0A * %7B@link alluxio.worker.netty.NettyDataServer%7D. It creates an %7B@link alluxio.worker.DataServer%7D%0A * instance based on Netty which is an asynchronous event-driven network application framework.%0A *%0A * The current read protocol is described by %7B@link alluxio.proto.datas
 erver
-%7D and %7B@link alluxio.worker.nio.NIODataServer%7D; netty
+.Protocol.ReadRequest%7D
 %0A * 
-is
+and
  the 
-default. To support both, a
+write protocol is described by
  %7B@l
@@ -1568,593 +1568,452 @@
 xio.
-worker.DataS
+proto.datas
 erver
-%7D interface is used that just%0A * defines how to start/stop, and get port details; to start, object init is used.%0A *%0A * The current read protocol is defined in %7B@link alluxio.worker.DataServerMessage%7D. This has two%0A * different types: read %7B@link alluxio.worker.DataServerMessage#createBlockRequestMessage%7D and%0A * write %7B@link alluxio.worker.DataServerMessage#createBlockResponseMessage%7D. Side note, the netty%0A * implementation does not use this class, but has defined two classes for the read and write case:%0A * %7B@link alluxio.network.protocol.RPCBlockReadRequest%7D,%0A *
+.Protocol.WriteRequest%7D,%0A * which are both defined by Protobuf to keep it extensible but also backward-compatible in the%0A * future.%0A *%0A * %3Ch2%3EThrift%3C/h2%3E%0A *%0A * The thrift service on worker side has been deprecated since v1.5. It used to serve%0A * metadata operations (with a few operations that effect the worker's cached memory) such as lock%0A * unlock, access, request space for blocks. It has been completely replaced by%0A * the
  %7B@l
@@ -2028,92 +2028,40 @@
 xio.
-net
 work
-.protocol.RPCBlockReadResponse%7D; theses classes are network compatibl
+er.DataServer%7D servic
 e.%0A */%0A
-%0A
 pack

Update package info for alluxio.worker