Open exalate-issue-sync[bot] opened 1 year ago
Neeraja Madabhushi commented: adding 2 separate issues to track between file systems local/hdfs
Neeraja Madabhushi commented: Not reproducible with build 1157
Geoffrey Anderson commented: The issue is currently reproducible on my system. Local hard disk filesystem ext4 in Linux. I cannot open saved Flow files at all. It's a Linux Ubuntu OS in Chrome browser. I am the only user on this host and it is my private workstation. Version info:
h2o.init(nthreads=-1,max_mem_size = '7g')
H2O is not running yet, starting it now...
Note: In case of errors look at the following log files: /tmp/RtmphDPCwU/h2o_ga_started_from_r.out /tmp/RtmphDPCwU/h2o_ga_started_from_r.err
java version "1.7.0_111" OpenJDK Runtime Environment (IcedTea 2.6.7) (7u111-2.6.7-0ubuntu0.14.04.3) OpenJDK 64-Bit Server VM (build 24.111-b01, mixed mode)
Starting H2O JVM and connecting: .. Connection successful!
R is connected to the H2O cluster:
H2O cluster uptime: 2 seconds 521 milliseconds
H2O cluster version: 3.10.0.7
H2O cluster version age: 20 days
H2O cluster name: H2O_started_from_R_ga_rbx068
H2O cluster total nodes: 1
H2O cluster total memory: 6.22 GB
H2O cluster total cores: 8
H2O cluster allowed cores: 8
H2O cluster healthy: TRUE
H2O Connection ip: localhost
H2O Connection port: 54321
H2O Connection proxy: NA
R Version: R version 3.3.1 (2016-06-21)
Google Chrome Version 53.0.2785.143 (64-bit)
ga@ga-EX58-UD4P:~$ uname -a Linux ga-EX58-UD4P 4.4.0-38-generic #57~14.04.1-Ubuntu SMP Tue Sep 6 17:20:43 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Terry commented: I am also able to reproduce this on amazon linux using h2o 3.10.0.9. If I point flow_dir to an ext4 volume, I receive an error in the UI trying to open a flow. If I point flow_dir to an ext3 volume it works perfectly. I cannot find a corresponding error in the h2o logs however.
Alert Error processing GET /3/NodePersistentStorage/notebook/test_flow
JIRA Issue Migration Info
Jira Issue: PUBDEV-873 Assignee: Neeraja Madabhushi Reporter: Neeraja Madabhushi State: Reopened Fix Version: N/A Attachments: Available (Count: 3) Development PRs: N/A
Attachments From Jira
Attachment Name: Screen Shot 2015-04-17 at 5.11.35 PM.png Attached By: Neeraja Madabhushi File Link:https://h2o-3-jira-github-migration.s3.amazonaws.com/PUBDEV-873/Screen Shot 2015-04-17 at 5.11.35 PM.png
Attachment Name: Screen Shot 2015-04-17 at 5.11.45 PM.png Attached By: Neeraja Madabhushi File Link:https://h2o-3-jira-github-migration.s3.amazonaws.com/PUBDEV-873/Screen Shot 2015-04-17 at 5.11.45 PM.png
Attachment Name: Screen Shot 2015-04-17 at 5.11.50 PM.png Attached By: Neeraja Madabhushi File Link:https://h2o-3-jira-github-migration.s3.amazonaws.com/PUBDEV-873/Screen Shot 2015-04-17 at 5.11.50 PM.png
Steps to reproduce :
1) Start h2o on hadoop
h2o-dev-builds/h2o-dev-0.3.0.1134-hdp2.1$ hadoop jar h2odriver.jar -nodes 4 -mapperXmx 40g -output April-17-1 -baseport 55555 -flow_dir hdfs:///user/neeraja/myflow-1
2) Go to Flow 3) File => Open 4) Get file from h2o-dev/h2o-docs/src/product/flow/packs/test/prostate.flow 5) Prompts say to choose file => open files 6) Error calling Upload /3/NodePersistentstorage/json/notebook/prostate {}
Error
04-17 17:10:13.608 172.16.2.181:55555 15931 # Session INFO: Method: GET , URI: /3/NodePersistentStorage.json/notebook/prostate, route: /3/NodePersistentStorage/(?.)/(?. ), parms: {name=prostate, category=notebook}
04-17 17:10:13.618 172.16.2.181:55555 15931 # Session WARN: Caught exception: HDFS IO Failure:
04-17 17:10:13.618 172.16.2.181:55555 15931 # Session WARN: accessed URI : hdfs:///user/neeraja/myflow-1/notebook/prostate configuration: Configuration: core-default.xml, core-site.xml, mapred-default.xml, mapred-site.xml, yarn-default.xml, yarn-site.xml, hdfs-default.xml, hdfs-site.xml; Stacktrace: [water.persist.PersistHdfs.open(PersistHdfs.java:391), water.persist.PersistManager.open(PersistManager.java:288), water.init.NodePersistentStorage.get_as_string(NodePersistentStorage.java:215), water.api.NodePersistentStorageHandler.get_as_string(NodePersistentStorageHandler.java:48), sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method), sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57), sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43), java.lang.reflect.Method.invoke(Method.java:606), water.api.Handler.handle(Handler.java:57), water.api.RequestServer.handle(RequestServer.java:665), water.api.RequestServer.serve(RequestServer.java:601), water.NanoHTTPD$HTTPSession.run(NanoHTTPD.java:433), java.lang.Thread.run(Thread.java:745)]
04-17 17:10:13.757 172.16.2.181:55555 15931 # Session ERRR: java.net.SocketException: Socket is closed