From notifications-return-42066-archive-asf-public=cust-asf.ponee.io@accumulo.apache.org Fri Feb 9 22:38:04 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 24658180654 for ; Fri, 9 Feb 2018 22:38:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 1013C160C5F; Fri, 9 Feb 2018 21:38:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 558E9160C3C for ; Fri, 9 Feb 2018 22:38:03 +0100 (CET) Received: (qmail 21337 invoked by uid 500); 9 Feb 2018 21:38:02 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 21325 invoked by uid 99); 9 Feb 2018 21:38:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Feb 2018 21:38:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id DEE71C0F79 for ; Fri, 9 Feb 2018 21:38:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id aV4a2z6fQlXB for ; Fri, 9 Feb 2018 21:38:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id C2ACE5F341 for ; Fri, 9 Feb 2018 21:38:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 60210E019D for ; Fri, 9 Feb 2018 21:38:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1780D21E85 for ; Fri, 9 Feb 2018 21:38:00 +0000 (UTC) Date: Fri, 9 Feb 2018 21:38:00 +0000 (UTC) From: "Michael Miller (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-4355) Provide more granular control for bulk import operations MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-4355?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1= 6359008#comment-16359008 ]=20 Michael Miller commented on ACCUMULO-4355: ------------------------------------------ I am wondering if some of these ideas would be better realized prior to cal= ling Accumulo API.=C2=A0 For example, looking at how the ingest process is = calling importDirectory() and restricting the size of directories passed to= the API could help. > Provide more granular control for bulk import operations > -------------------------------------------------------- > > Key: ACCUMULO-4355 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4355 > Project: Accumulo > Issue Type: Wish > Components: master, tserver > Reporter: Shawn Walker > Assignee: Shawn Walker > Priority: Major > Fix For: 2.0.0 > > > Accumulo currently provides mechanisms to initiate bulk imports and to li= st bulk imports in progress. Scheduling of bulk import requests is not ent= irely deterministic, and most of the execution of a bulk-import request is = done in a non-preemptable manner. As such, any bulk import which takes ver= y long to complete can block bulk imports with higher operational priority = for significant periods. > To better support bulk-import-heavy applications, it would be nice if Acc= umulo would offer additional mechanisms for controlling the scheduling and = execution of bulk imports, such as the abilities to: > * Pause/resume bulk import in progress. > * Prioritize/reprioritize bulk import requests. > * Cancel bulk import in progress. If possible, cancelling a partially co= mpleted bulk import request should result in a rollback of changes. That i= s, a bulk import should either succeed or make no changes. > Additionally, for multitenant situations, it would be nice if Accumulo wo= uld: > * Provide multiple queues for bulk import requests. Each queue would hav= e its requests worked serially in priority order. Requests in separate que= ues should be worked in parallel, or have time distributed among the queues= in some manner as to make work appear roughly parallel. > ---- > Implementation-wise, I'm thinking of rewriting much of the current bulk-l= oading logic. While the current logic depends upon multiple threads execut= ing (potentially long-duration) blocking RPC calls, I'd like to move to a m= ore event-driven/message-passing model backed by a persistent state machine= . > Current ideas I'm playing around with (very tentative) > * Creating a new table {{accumulo.bulk_load_queues}} to keep track of bul= k load progress. > * Distributing bulk load orchestration via a mechanism similar to tablet = assignment instead of the current blocking RPC calls (LoadFiles.java:156). > * Implementing something akin to a two-phase commit to achieve rollback b= ehavior on failure. -- This message was sent by Atlassian JIRA (v7.6.3#76005)