accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-4458) lock contention around configuration settings impacts tablet server performance
Date Wed, 14 Sep 2016 23:58:21 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-4458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15491815#comment-15491815
] 

Josh Elser commented on ACCUMULO-4458:
--------------------------------------

{code}
+  /**
+   * Properties we check the value of within the TabletServer request handling or maintenance
processing loops.
+   */
+  public static final EnumSet<Property> HOT_PATH_PROPERTIES = EnumSet.of(Property.TSERV_CLIENT_TIMEOUT,
Property.TSERV_TOTAL_MUTATION_QUEUE_MAX,
+      Property.TSERV_ARCHIVE_WALOGS, Property.GC_TRASH_IGNORE, Property.TSERV_MAJC_DELAY,
Property.TABLE_MINC_LOGS_MAX, Property.TSERV_MAJC_MAXCONCURRENT,
+      Property.REPLICATION_WORKER_THREADS, Property.TABLE_DURABILITY, Property.INSTANCE_ZK_TIMEOUT,
Property.TABLE_CLASSPATH);
+
{code}

It seems like it would be more simple if we just extracted all Accumulo properties (instead
of this reduced list). Is there a big impact on memory for this? What about if we remove any
that are still the default value (and let them be represented by the DefaultConfiguration)?
My initial concern would be that we miss some, or add new "hot" properties, and we sign up
to having to maintain this list.

> lock contention around configuration settings impacts tablet server performance
> -------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-4458
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4458
>             Project: Accumulo
>          Issue Type: Bug
>          Components: tserver
>    Affects Versions: 1.7.1, 1.8.0
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Critical
>             Fix For: 1.7.3, 1.8.1, 2.0.0
>
>         Attachments: ACCUMULO-4458-1.7.v1.patch
>
>
> While investigating a pretty severe performance regression comparing YCSB against 1.6
and 1.7, I found a fair bit of lock contention around getting configuration values. This was
improved by ACCUMULO-4388, but various threads eventually all started contending on the configuration
values expected from the site xml files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message