hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rushabh S Shah (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-12667) KMSClientProvider#ValueQueue does synchronous fetch of edeks in background async thread.
Date Mon, 16 Oct 2017 18:19:00 GMT
Rushabh S Shah created HDFS-12667:

             Summary: KMSClientProvider#ValueQueue does synchronous fetch of edeks in background
async thread.
                 Key: HDFS-12667
                 URL: https://issues.apache.org/jira/browse/HDFS-12667
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: encryption, kms
    Affects Versions: 3.0.0-alpha4
            Reporter: Rushabh S Shah
            Assignee: Rushabh S Shah

There are couple of issues in KMSClientProvider#ValueQueue.
  private final LoadingCache<String, LinkedBlockingQueue<E>> keyQueues;
  // Stripped rwlocks based on key name to synchronize the queue from
  // the sync'ed rw-thread and the background async refill thread.
  private final List<ReadWriteLock> lockArray =
      new ArrayList<>(LOCK_ARRAY_SIZE);
It hashes the key name into 16 buckets.
In the code chunk below,

public List<E> getAtMost(String keyName, int num) throws IOException,
      ExecutionException {
        E val = keyQueue.poll();

  private void submitRefillTask(final String keyName,
      final Queue<E> keyQueue) throws InterruptedException {
              writeLock(keyName); // It holds the write lock while the key is being asynchronously
fetched. So the read requests for all the keys that hashes to this bucket will essentially
be blocked.
              try {
                if (keyQueue.size() < threshold && !isCanceled()) {
                  refiller.fillQueueForKey(name, keyQueue,
                      cacheSize - keyQueue.size());
              } finally {
According to above code chunk, if two keys (lets say key1 and key2) hashes to the same bucket
(between 1 and 16), then if key1 is asynchronously being refetched then all the getKey for
key2 will be blocked.

2. Due to stripped rw locks, the asynchronous behavior of refill keys is now synchronous to
other handler threads.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message