Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HDFS FileSystem Cache Problem #418

Closed
HeryLong opened this issue Mar 1, 2019 · 2 comments
Closed

HDFS FileSystem Cache Problem #418

HeryLong opened this issue Mar 1, 2019 · 2 comments

Comments

@HeryLong
Copy link

HeryLong commented Mar 1, 2019

Recently, I'm working on an ClosedChannelException of kafka-connect-hdfs, and I find that

  1. WALFile.java have fellowing code
fs = filename.getFileSystem(conf);

...

log.error("Failed creating a WAL Reader: " + re.getMessage());
if (re.getClassName().equals(WALConstants.LEASE_EXCEPTION_CLASS_NAME)) {
  if (fs != null) {
    fs.close();
  }
}

link to WALFile.java#L146

  1. StringRecordWriterProvider.java have fellowing code
final OutputStream out = path.getFileSystem(conf.getHadoopConfiguration()).create(path);

...

writer.close();

link to StringRecordWriterProvider.java#L64

So, while working under hdfs default configuration fs.hdfs.impl.disable.cache=false, will these code have effect to each other, such as one close HDFS FileSystem, which may lead to the other one get ClosedChannelException? Or, we should set fs.hdfs.impl.disable.cache=true while using this plugin always ?

Any one have some explication for this? 3ks

@cyrusv
Copy link
Contributor

cyrusv commented Apr 19, 2019

@HeryLong , it seems you're seeing this issue: #141 (comment)

The best solution here is to upgrade HDFS. If that's not an option, then it is recommended to turn caching off in HDFS as you suggest. H

@HeryLong
Copy link
Author

@cyrusv
ok, got it. thank you for your comment~

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants