{"action":"created","issue":{"url":"https://api.github.com/repos/tuplejump/FiloDB/issues/84","repository_url":"https://api.github.com/repos/tuplejump/FiloDB","labels_url":"https://api.github.com/repos/tuplejump/FiloDB/issues/84/labels{/name}","comments_url":"https://api.github.com/repos/tuplejump/FiloDB/issues/84/comments","events_url":"https://api.github.com/repos/tuplejump/FiloDB/issues/84/events","html_url":"https://github.com/tuplejump/FiloDB/issues/84","id":144006137,"number":84,"title":"Futures timed out after [5 seconds]","user":{"login":"java8964","id":1430098,"avatar_url":"https://avatars.githubusercontent.com/u/1430098?v=3","gravatar_id":"","url":"https://api.github.com/users/java8964","html_url":"https://github.com/java8964","followers_url":"https://api.github.com/users/java8964/followers","following_url":"https://api.github.com/users/java8964/following{/other_user}","gists_url":"https://api.github.com/users/java8964/gists{/gist_id}","starred_url":"https://api.github.com/users/java8964/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/java8964/subscriptions","organizations_url":"https://api.github.com/users/java8964/orgs","repos_url":"https://api.github.com/users/java8964/repos","events_url":"https://api.github.com/users/java8964/events{/privacy}","received_events_url":"https://api.github.com/users/java8964/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":22,"created_at":"2016-03-28T15:38:06Z","updated_at":"2016-04-01T13:45:46Z","closed_at":"2016-03-31T16:57:04Z","body":"I am trying to test FiloDB 0.2 with a 6 nodes C* (DSE 4.8.5) cluster, running Spark 1.5.2.\r\n\r\nThe 100k sample data coming with FiloDB works fine, but when I tried to load 50M data of our use case, with a dataset I come out of POC, I got the following error message when trying to do this step:\r\n\r\nnewDF.write.format(\"filodb.spark\").option(\"dataset\", \"poc1\").option(\"row_keys\", \"Email\").option(\"segment_key\",\"Domain\").option(\"partition_keys\",\"Partition\").mode(SaveMode.Overwrite).save()\r\n\r\njava.util.concurrent.TimeoutException: Futures timed out after [5 seconds]\r\n\tat scala.concurrent.impl.Promise$DefaultPromise.ready(Promise.scala:219)\r\n\tat scala.concurrent.impl.Promise$DefaultPromise.result(Promise.scala:223)\r\n\tat scala.concurrent.Await$$anonfun$result$1.apply(package.scala:107)\r\n\tat scala.concurrent.BlockContext$DefaultBlockContext$.blockOn(BlockContext.scala:53)\r\n\tat scala.concurrent.Await$.result(package.scala:107)\r\n\tat filodb.spark.FiloRelation$.parse(FiloRelation.scala:36)\r\n\tat filodb.spark.FiloRelation$.actorAsk(FiloRelation.scala:42)\r\n\tat filodb.spark.package$FiloContext.createNewDataset(package.scala:165)\r\n\tat filodb.spark.package$FiloContext.createOrUpdateDataset(package.scala:216)\r\n\tat filodb.spark.package$FiloContext.saveAsFilo(package.scala:268)\r\n\tat filodb.spark.DefaultSource.createRelation(DefaultSource.scala:53)\r\n\tat org.apache.spark.sql.execution.datasources.ResolvedDataSource$.apply(ResolvedDataSource.scala:170)\r\n\tat org.apache.spark.sql.DataFrameWriter.save(DataFrameWriter.scala:146)\r\n\tat $iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.<init>(<console>:25)\r\n\tat $iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.<init>(<console>:30)\r\n\tat $iwC$$iwC$$iwC$$iwC$$iwC$$iwC.<init>(<console>:32)\r\n\tat $iwC$$iwC$$iwC$$iwC$$iwC.<init>(<console>:34)\r\n\tat $iwC$$iwC$$iwC$$iwC.<init>(<console>:36)\r\n\tat $iwC$$iwC$$iwC.<init>(<console>:38)\r\n\tat $iwC$$iwC.<init>(<console>:40)\r\n\tat $iwC.<init>(<console>:42)\r\n\tat <init>(<console>:44)\r\n\tat .<init>(<console>:48)\r\n\tat .<clinit>(<console>)\r\n\tat .<init>(<console>:7)\r\n\tat .<clinit>(<console>)\r\n\r\nI am not sure this related to our C* settings, but it looks like a timeout from the FiloDB, but I don't see any configuration in the application.conf can adjust it.\r\n\r\nWhat setting I should change for this?\r\n\r\nThanks"},"comment":{"url":"https://api.github.com/repos/tuplejump/FiloDB/issues/comments/204401456","html_url":"https://github.com/tuplejump/FiloDB/issues/84#issuecomment-204401456","issue_url":"https://api.github.com/repos/tuplejump/FiloDB/issues/84","id":204401456,"user":{"login":"java8964","id":1430098,"avatar_url":"https://avatars.githubusercontent.com/u/1430098?v=3","gravatar_id":"","url":"https://api.github.com/users/java8964","html_url":"https://github.com/java8964","followers_url":"https://api.github.com/users/java8964/followers","following_url":"https://api.github.com/users/java8964/following{/other_user}","gists_url":"https://api.github.com/users/java8964/gists{/gist_id}","starred_url":"https://api.github.com/users/java8964/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/java8964/subscriptions","organizations_url":"https://api.github.com/users/java8964/orgs","repos_url":"https://api.github.com/users/java8964/repos","events_url":"https://api.github.com/users/java8964/events{/privacy}","received_events_url":"https://api.github.com/users/java8964/received_events","type":"User","site_admin":false},"created_at":"2016-04-01T13:45:46Z","updated_at":"2016-04-01T13:45:46Z","body":"Hi, Evan:\nIs there mailing list or google group for FiloDB? I searched, but didn't find any.\nYong\n\nDate: Thu, 31 Mar 2016 23:42:55 -0700\nFrom: notifications@github.com\nTo: FiloDB@noreply.github.com\nCC: java8964@hotmail.com\nSubject: Re: [tuplejump/FiloDB] Futures timed out after [5 seconds] (#84)\n\nYong,\n\n\n\nThanks so much for the kind words.\n\n\n\n1) 8k data missing - I’m in the middle of adding a stress test to debug and make sure no data is missing.\n\n2) what do you mean that joining is causing problems?   Joining will be slower for sure, Spark’s join optimization is not very good.   I would make sure that you are pushing down all predicates.  Is the other table also FiloDB, or regular Cassandra, or something else?\n\n\n\nI wrote a blog post about doing fast joins recently.\n\n\n\nI will investigate the tungsten sort failure still.   After Spark 1.6 you can’t turn off tungsten any more, so we do want to get the sort working.\n\n\n\n\n\n> On Mar 31, 2016, at 7:06 AM, Yong Zhang <notifications@github.com> wrote:\n\n> \n\n> Hi, Evan:\n\n> I succeeded loading 50M data. The important trick is to avoid \"Tungsten sort\". I am very impressive of the querying speed. I am very confident that if Filo DB matures enough, there will be lots of use cases can benefit from it.\n\n> \n\n> There are 2 issues I found out so far, but I understand for a version 0.2 release, it is normal:\n\n> 1) I loaded 10M first, then loaded 50M (include the first 10M rows) again. The total rows are 49991285 after 2nd load. There are 8k data gone.\n\n> 2) Even self querying this dataset is super fast, but joining with another small dataset in the Spark causing problems.\n\n> \n\n> I will try to understand more about FiloDB, but thanks for such an amazing open source idea.\n\n> \n\n> Let me know what I can help for maturing it.\n\n> \n\n> Yong\n\n> \n\n> —\n\n> You are receiving this because you commented.\n\n> Reply to this email directly or view it on GitHub <https://github.com/tuplejump/FiloDB/issues/84#issuecomment-203954949>\n\n\n\n\n\n—\nYou are receiving this because you modified the open/close state.\nReply to this email directly or view it on GitHub\n\n\n  \n  \n\n\n \t\t \t   \t\t  "}}