accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Wall (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ACCUMULO-4657) BulkImport Performance Bottleneck
Date Tue, 20 Jun 2017 20:45:00 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Wall resolved ACCUMULO-4657.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0
                   1.8.2
                   1.7.4

> BulkImport Performance Bottleneck
> ---------------------------------
>
>                 Key: ACCUMULO-4657
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4657
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: Matt Peterson
>            Assignee: Matt Peterson
>            Priority: Minor
>             Fix For: 1.7.4, 1.8.2, 2.0.0
>
>          Time Spent: 4h 50m
>  Remaining Estimate: 0h
>
> Outputting every "loaded" entry in the table is excessive, especially for tables with
multiple simultaneous bulk imports and multiple references to the same file.  This can cause
performance problems.  Even when the log level was reduced, there was blocking within log4j.
 By doing that check once outside the loop and only logging at trace level, bulk import performance
improves for such usages.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message