You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Luciano Afranllie (JIRA)" <ji...@apache.org> on 2016/07/28 02:25:20 UTC

[jira] [Updated] (KAFKA-3987) Allow configuration of the hash algorithm used by the LogCleaner's offset map

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

Luciano Afranllie updated KAFKA-3987:
-------------------------------------
    Reviewer: Shikhar Bhushan
      Status: Patch Available  (was: Open)

> Allow configuration of the hash algorithm used by the LogCleaner's offset map
> -----------------------------------------------------------------------------
>
>                 Key: KAFKA-3987
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3987
>             Project: Kafka
>          Issue Type: Improvement
>          Components: config
>            Reporter: Luciano Afranllie
>            Priority: Minor
>             Fix For: 0.10.1.0
>
>
> In order to be able to do deployments of Kafka that are FIPS 140-2 (https://en.wikipedia.org/wiki/FIPS_140-2) complaint one of the requirements is not to use MD5.
> Kafka is using MD5 to hash message keys in the offset map (SkimpyOffsetMap) used by the log cleaner.
> The idea is to be able to configure this hash algorithm to something allowed by FIPS using a new configuration property.
> The property could be named "log.cleaner.hash.algorithm" with a default value equal to "MD5" and the idea is to use it in the constructor of CleanerConfig.



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