Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 30271100A1 for ; Wed, 17 Jul 2013 14:34:53 +0000 (UTC) Received: (qmail 98918 invoked by uid 500); 17 Jul 2013 14:34:51 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 98517 invoked by uid 500); 17 Jul 2013 14:34:50 -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 98448 invoked by uid 99); 17 Jul 2013 14:34:48 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Jul 2013 14:34:48 +0000 Date: Wed, 17 Jul 2013 14:34:48 +0000 (UTC) From: "Keith Turner (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ACCUMULO-1188) Sandbox iterators MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Turner updated ACCUMULO-1188: ----------------------------------- Attachment: ACCUMULO-1188_fig1.png I was thinking about how this could be done and had the following thoughts : * A tablet should advertise different ports for reading and writing, so that reader can go directly to the process running scans. * The process running the scan should also contain the cache. I attached fig 1 that shows the data flows I was thinking of. I have also started to think that we should not pursue this approach or running compactions and scans in separate processes. I think that if ACCUMULO-1454 is implemented, that it may solve the problem this ticket is trying to solve. If an iterator gets stuck in an infinite loop ACCUMULO-1454 makes it possible to restart the tserver and avoid disruption. I am thinking the following should be done. * Use ACCUMULO-1345 and ACCUMULO-1454 to restart tservers with stuck compactions/scans. * Need to blacklist tablets that repeatedly fail ACCUMULO-1570 Is there any reason to pursue this ticket if we restart tservers and blacklist tablets? Even if we run user iterators in a separate process, we will still need to blacklist tablets and restart those separate processes. The only thing its seems to help with is avoiding walog recovery. Are there other benefits? > Sandbox iterators > ----------------- > > Key: ACCUMULO-1188 > URL: https://issues.apache.org/jira/browse/ACCUMULO-1188 > Project: Accumulo > Issue Type: Bug > Reporter: Keith Turner > Fix For: 1.6.0 > > Attachments: ACCUMULO-1188_fig1.png > > > It's possible that a user iterator can bring down a tablet server. For example if it has an OOM or creates too many threads. It would be nice if iterators could be sandboxed in some way. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira