Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E2316108F0 for ; Wed, 9 Sep 2015 09:47:13 +0000 (UTC) Received: (qmail 8645 invoked by uid 500); 9 Sep 2015 09:46:50 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 8568 invoked by uid 500); 9 Sep 2015 09:46:50 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 8557 invoked by uid 99); 9 Sep 2015 09:46:49 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Sep 2015 09:46:49 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 348C118096B for ; Wed, 9 Sep 2015 09:46:49 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.28 X-Spam-Level: *** X-Spam-Status: No, score=3.28 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id NC-APShrnoF9 for ; Wed, 9 Sep 2015 09:46:48 +0000 (UTC) Received: from mail-yk0-f182.google.com (mail-yk0-f182.google.com [209.85.160.182]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 78D2320383 for ; Wed, 9 Sep 2015 09:46:47 +0000 (UTC) Received: by ykcf206 with SMTP id f206so6362894ykc.3 for ; Wed, 09 Sep 2015 02:46:46 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=V7mTzdFOnDFUNjQ4qTz1gd/3xioVe4KfBPxiM7gjKtE=; b=J3hLpFSWgyK9QQERegokmevJFHs9YVR/aCke4iRPEQrHnuVw1vURtvB5fjFj7fCJWe je9Hzkoec2YFLzIhmuqu80EBwqgzpRvf5NY9eIohnI2HRpzC2fhZKJDi7OcTPaJOBz9l WLQONvFsDrMtccKzGPO8ITMXzsnzzln+gBQFJdDFgRUP+vsSz0bs4GzahzLtuy6lajQJ ma3QJxHenUgdZnE1IsVD96Tn0lb69fnfW4tjcP8Isrru9lJgyv4ITO9MN/ga43meOHuy vxMdmjcFVkMYnjiZPeljmBgo4CEeStS0rJkfXA6hPC+lRDklEW+KIAaRLXhQy6VGsEKa q7qw== X-Gm-Message-State: ALoCoQncOdixN3KqtXgn7/y7adSeZfXvskwe6Mnixeh9H8HmnPlF6hb0BWuxCMgKXFIViNWr87gy MIME-Version: 1.0 X-Received: by 10.13.231.69 with SMTP id q66mr36115324ywe.69.1441792005929; Wed, 09 Sep 2015 02:46:45 -0700 (PDT) Received: by 10.13.219.195 with HTTP; Wed, 9 Sep 2015 02:46:45 -0700 (PDT) Date: Wed, 9 Sep 2015 11:46:45 +0200 Message-ID: Subject: Avoiding a full with user requests From: =?UTF-8?B?TG/Dr2MgQ2hhbmVs?= To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=94eb2c0818025ab5de051f4d5c89 --94eb2c0818025ab5de051f4d5c89 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi all, As I'm trying to secure a cluster with HBase, I was wondering if somehow there is a possibility that a user can monopolize HBase ability to write data by sending a lot of data into HBase, Is there a queue mechanism or something to handle such an issue ? Thanks in advance for your help, Regards, Lo=C3=AFc Lo=C3=AFc CHANEL Engineering student at TELECOM Nancy Trainee at Worldline - Villeurbanne --94eb2c0818025ab5de051f4d5c89--