accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-4458) lock contention around configuration settings impacts tablet server performance
Date Thu, 15 Sep 2016 00:05:20 GMT


Sean Busbey commented on ACCUMULO-4458:

Right now I do extract all of the properties that are set. This is just the list where we
say to always default ot the parent if they weren't set. This effectively means we let them
be represented by DefaultConfiguration.

The presence of the "only use this for test" {{set}} method on SiteConfiguration leads me
to presume some set of tests must be relying on the ability to poke values into the Hadoop
Configuration object. As much as I'd like to just make this all read-only and throw away the
Hadoop Configuration object entirely after construction, I didn't want to muddle things with
possible test failures or having to rework them to no longer presume they can mutate on-disk
configuration values.

> lock contention around configuration settings impacts tablet server performance
> -------------------------------------------------------------------------------
>                 Key: ACCUMULO-4458
>                 URL:
>             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

View raw message