java.lang.IllegalArgumentException

Dataset nfs://home/0xcustomer/home-0xdiag-datasets/manyfiles-nflx-gz/file_100.dat.gz is already in use. Unable to use it now. Consider using a different destination name.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web20318

  • via JIRA by Kevin Normoyle, 1 year ago
    Dataset nfs://home/0xcustomer/home-0xdiag-datasets/manyfiles-nflx-gz/file_100.dat.gz is already in use. Unable to use it now. Consider using a different destination name.
  • via JIRA by Kevin Normoyle, 1 year ago
    Dataset nfs://home/0xcustomer/home-0xdiag-datasets/manyfiles-nflx-gz/file_100.dat.gz is already in use. Unable to use it now. Consider using a different destination name.
  • via JIRA by Tom Kraljevic, 1 year ago
    Dataset .... is already in use. Unable to use it now. Consider using a different destination name.
  • Stack trace

    • java.lang.IllegalArgumentException: Dataset nfs://home/0xcustomer/home-0xdiag-datasets/manyfiles-nflx-gz/file_100.dat.gz is already in use. Unable to use it now. Consider using a different destination name. at water.Lockable$PriorWriteLock.atomic(Lockable.java:83) at water.Lockable$PriorWriteLock.atomic(Lockable.java:72) at water.TAtomic.atomic(TAtomic.java:19) at water.Atomic.compute2(Atomic.java:57) at water.DTask.dinvoke(DTask.java:78) at water.RPC$RPCCall.compute2(RPC.java:276) at water.H2O$H2OCountedCompleter.compute(H2O.java:712) at jsr166y.CountedCompleter.exec(CountedCompleter.java:429) at jsr166y.ForkJoinTask.doExec(ForkJoinTask.java:263) at jsr166y.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:974) at jsr166y.ForkJoinPool.runWorker(ForkJoinPool.java:1477) at jsr166y.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:104)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.