[
https://issues.apache.org/jira/browse/SPARK-19995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972373#comment-15972373
]
meiyoula commented on SPARK-19995:
--
Will the token be expired?
> Using real user to connect
[
https://issues.apache.org/jira/browse/SPARK-19943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15923425#comment-15923425
]
meiyoula commented on SPARK-19943:
--
[~srowen] Do you think this vulnerability affects spark?
>
meiyoula created SPARK-19943:
Summary: commons-collections has vulnerability: CVE-2015-6420
Key: SPARK-19943
URL: https://issues.apache.org/jira/browse/SPARK-19943
Project: Spark
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SPARK-10721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15857225#comment-15857225
]
meiyoula commented on SPARK-10721:
--
Hi [~srowen], may I ask a question. When File.delete() returns
[
https://issues.apache.org/jira/browse/SPARK-19250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-19250:
-
Description:
1. starting thriftserver in security mode, set hive.metastore.uris to hive
metastore uri,
[
https://issues.apache.org/jira/browse/SPARK-19250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827320#comment-15827320
]
meiyoula commented on SPARK-19250:
--
[~rxin] I think you may understand this bug.
I find u set
[
https://issues.apache.org/jira/browse/SPARK-19250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-19250:
-
Labels: security-issue (was: )
> In security cluster, spark beeline connect to hive metastore failed
>
[
https://issues.apache.org/jira/browse/SPARK-19250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824896#comment-15824896
]
meiyoula edited comment on SPARK-19250 at 1/17/17 3:47 AM:
---
[~vanzin] I find
[
https://issues.apache.org/jira/browse/SPARK-19250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15824896#comment-15824896
]
meiyoula commented on SPARK-19250:
--
[~vanzin] I found SPARK-13478 is a similar bug, you has resolved it.
[
https://issues.apache.org/jira/browse/SPARK-19250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-19250:
-
Description:
1. starting thriftserver in security mode, set hive.metastore.uris to hive
metastore uri,
[
https://issues.apache.org/jira/browse/SPARK-19250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-19250:
-
Description: 1. starting thriftserver in security mode, set
hive.metastore.uris to hive metastore uri,
[
https://issues.apache.org/jira/browse/SPARK-19250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-19250:
-
Environment: (was: 1. Security cluster
2.Set hive.metastore.uris to hivr metastore uri)
> In
meiyoula created SPARK-19250:
Summary: In security cluster, spark beeline connect to hive
metastore failed
Key: SPARK-19250
URL: https://issues.apache.org/jira/browse/SPARK-19250
Project: Spark
[
https://issues.apache.org/jira/browse/SPARK-18997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15803270#comment-15803270
]
meiyoula commented on SPARK-18997:
--
Sorry, I need help
> Recommended upgrade libthrift to 0.9.3
>
[
https://issues.apache.org/jira/browse/SPARK-18997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15779389#comment-15779389
]
meiyoula commented on SPARK-18997:
--
I think it is mainly consist in Hive. Now Hive has upgrade to 0.9.3
meiyoula created SPARK-18997:
Summary: Recommended upgrade libthrift to 0.9.3
Key: SPARK-18997
URL: https://issues.apache.org/jira/browse/SPARK-18997
Project: Spark
Issue Type: Bug
meiyoula created SPARK-18839:
Summary: Executor is active on web, but actually is dead
Key: SPARK-18839
URL: https://issues.apache.org/jira/browse/SPARK-18839
Project: Spark
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SPARK-18664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15711307#comment-15711307
]
meiyoula commented on SPARK-18664:
--
please refer to
[
https://issues.apache.org/jira/browse/SPARK-18664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-18664:
-
Description:
This was flagged a while ago during a routine security scan(AWVS): the
HTTP-based Spark
[
https://issues.apache.org/jira/browse/SPARK-18664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15710591#comment-15710591
]
meiyoula commented on SPARK-18664:
--
[~srowen] It is similar to SPARK-5983, should we fix it?
> Don't
meiyoula created SPARK-18664:
Summary: Don't respond to HTTP OPTIONS in HTTP-based UIs
Key: SPARK-18664
URL: https://issues.apache.org/jira/browse/SPARK-18664
Project: Spark
Issue Type:
meiyoula created SPARK-18586:
Summary: netty-3.8.0.Final.jar has vulnerability CVE-2014-3488
and CVE-2014-0193
Key: SPARK-18586
URL: https://issues.apache.org/jira/browse/SPARK-18586
Project: Spark
[
https://issues.apache.org/jira/browse/SPARK-15170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-15170:
-
Description:
No matter how long the expire idle time of executor, the log just says "it has
been idle
[
https://issues.apache.org/jira/browse/SPARK-15170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15273820#comment-15273820
]
meiyoula commented on SPARK-15170:
--
When the executor has cached block, it should be
meiyoula created SPARK-15170:
Summary: Log error message in ExecutorAllocationManager
Key: SPARK-15170
URL: https://issues.apache.org/jira/browse/SPARK-15170
Project: Spark
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SPARK-14486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-14486:
-
Description:
For partition table, when partition rdds do some maps, the rdd number will
multiple grow.
[
https://issues.apache.org/jira/browse/SPARK-14486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-14486:
-
Attachment: screenshot-1.png
> For partition table, the dag occurs oom because of too many same rdds
>
[
https://issues.apache.org/jira/browse/SPARK-14486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231942#comment-15231942
]
meiyoula commented on SPARK-14486:
--
I think it's a bug, when there are too many partition rdds, the dag
[
https://issues.apache.org/jira/browse/SPARK-14486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-14486:
-
Issue Type: Bug (was: Improvement)
> For partition table, the dag occurs oom because of too many same
[
https://issues.apache.org/jira/browse/SPARK-14486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231920#comment-15231920
]
meiyoula edited comment on SPARK-14486 at 4/8/16 9:25 AM:
--
[~andrewor14] Can you
[
https://issues.apache.org/jira/browse/SPARK-14486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15231920#comment-15231920
]
meiyoula commented on SPARK-14486:
--
[~andrewor14]
> For partition table, the dag occurs oom because of
meiyoula created SPARK-14486:
Summary: For partition table, the dag occurs oom because of too
many same rdds
Key: SPARK-14486
URL: https://issues.apache.org/jira/browse/SPARK-14486
Project: Spark
[
https://issues.apache.org/jira/browse/SPARK-14403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula closed SPARK-14403.
Resolution: Resolved
> the dag of a stage may has too many same chid cluster, and result to gc
>
meiyoula created SPARK-14403:
Summary: the dag of a stage may has too many same chid cluster,
and result to gc
Key: SPARK-14403
URL: https://issues.apache.org/jira/browse/SPARK-14403
Project: Spark
[
https://issues.apache.org/jira/browse/SPARK-13112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15217362#comment-15217362
]
meiyoula commented on SPARK-13112:
--
I agree with it. When CoarseGrainedExecutorBackend receives
[
https://issues.apache.org/jira/browse/SPARK-13060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15217359#comment-15217359
]
meiyoula commented on SPARK-13060:
--
When CoarseGrainedExecutorBackend receives RegisterExecutorResponse
[
https://issues.apache.org/jira/browse/SPARK-13060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-13060:
-
Comment: was deleted
(was: When CoarseGrainedExecutorBackend receives RegisterExecutorResponse slow
[
https://issues.apache.org/jira/browse/SPARK-13060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15217360#comment-15217360
]
meiyoula commented on SPARK-13060:
--
When CoarseGrainedExecutorBackend receives RegisterExecutorResponse
meiyoula created SPARK-14233:
Summary: NativeThread.signal(Native Method): No such file or
directory
Key: SPARK-14233
URL: https://issues.apache.org/jira/browse/SPARK-14233
Project: Spark
Issue
meiyoula created SPARK-14228:
Summary: Lost executor of RPC disassociated, and occurs exception:
Could not find CoarseGrainedScheduler or it has been stopped
Key: SPARK-14228
URL:
[
https://issues.apache.org/jira/browse/SPARK-14192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15215273#comment-15215273
]
meiyoula commented on SPARK-14192:
--
The master branch of 2016/3/28
> Executor is dead in Driver but
meiyoula created SPARK-14192:
Summary: Executor is dead in Driver but alive in AM when driver
losts rpc with executor, but executor is alive.
Key: SPARK-14192
URL: https://issues.apache.org/jira/browse/SPARK-14192
[
https://issues.apache.org/jira/browse/SPARK-12493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula reopened SPARK-12493:
--
> Can't open "details" span of ExecutionsPage in IE11
>
[
https://issues.apache.org/jira/browse/SPARK-12493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073342#comment-15073342
]
meiyoula commented on SPARK-12493:
--
[~sowen]I think it's simply to reproduce this problem.
I don't know
[
https://issues.apache.org/jira/browse/SPARK-12493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073342#comment-15073342
]
meiyoula edited comment on SPARK-12493 at 12/29/15 1:31 AM:
[~sowen], I think
[
https://issues.apache.org/jira/browse/SPARK-12493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-12493:
-
Description:
Reproduce steps:
1. sbin/start-thriftserver.sh
2. Beeline connect to thriftserver, and run
[
https://issues.apache.org/jira/browse/SPARK-12493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-12493:
-
Attachment: IE version.png
> Can't open "details" span of ExecutionsPage in IE11
>
[
https://issues.apache.org/jira/browse/SPARK-12492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula reopened SPARK-12492:
--
Still has this problem
> SQL page of Spark-sql is always blank
> --
[
https://issues.apache.org/jira/browse/SPARK-12492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15073378#comment-15073378
]
meiyoula commented on SPARK-12492:
--
[~srowen], I still met this problem using the latest master branch.
meiyoula created SPARK-12492:
Summary: SQL page of Spark-sql is always blank
Key: SPARK-12492
URL: https://issues.apache.org/jira/browse/SPARK-12492
Project: Spark
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SPARK-12493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-12493:
-
Component/s: Web UI
> Can't open "details" span of ExecutionsPage in IE11
>
[
https://issues.apache.org/jira/browse/SPARK-12493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-12493:
-
Attachment: screenshot-1.png
> Can't open "details" span of ExecutionsPage in IE11
>
meiyoula created SPARK-12493:
Summary: Can't open "details" span of ExecutionsPage in IE11
Key: SPARK-12493
URL: https://issues.apache.org/jira/browse/SPARK-12493
Project: Spark
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SPARK-12492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-12492:
-
Attachment: screenshot-1.png
> SQL page of Spark-sql is always blank
>
[
https://issues.apache.org/jira/browse/SPARK-11652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15046619#comment-15046619
]
meiyoula commented on SPARK-11652:
--
[~darabos] Can you have a look on the patch merged by owen, I think
meiyoula created SPARK-12142:
Summary: Can't request executor when container allocator is not
ready
Key: SPARK-12142
URL: https://issues.apache.org/jira/browse/SPARK-12142
Project: Spark
Issue
meiyoula created SPARK-12143:
Summary: When column type is binary, select occurs
ClassCastExcption in Beeline.
Key: SPARK-12143
URL: https://issues.apache.org/jira/browse/SPARK-12143
Project: Spark
meiyoula created SPARK-11950:
Summary: Exception throws when executing “exit;” in spark-sql
Key: SPARK-11950
URL: https://issues.apache.org/jira/browse/SPARK-11950
Project: Spark
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SPARK-11811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-11811:
-
Description:
1. Starting ThriftServer
2. Using below command to connect server：
./beeline -u
meiyoula created SPARK-11811:
Summary: Database can't be changed if it is specified in url
Key: SPARK-11811
URL: https://issues.apache.org/jira/browse/SPARK-11811
Project: Spark
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SPARK-11811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-11811:
-
Description:
1. Starting ThriftServer
2. Using below command to connect server：
./beeline -u
[
https://issues.apache.org/jira/browse/SPARK-11334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-11334:
-
Summary: numRunningTasks can't be less than 0, or it will affect executor
allocation (was:
[
https://issues.apache.org/jira/browse/SPARK-11334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-11334:
-
Description:
With *Dynamic Allocation* function, a task failed over *maxFailure* time, all
the
meiyoula created SPARK-10586:
Summary: BlockManager ca't be removed when it is re-registered,
then disassociats
Key: SPARK-10586
URL: https://issues.apache.org/jira/browse/SPARK-10586
Project: Spark
meiyoula created SPARK-10311:
Summary: In cluster mode, AppId and AttemptId should be update
when ApplicationMaster is new
Key: SPARK-10311
URL: https://issues.apache.org/jira/browse/SPARK-10311
Project:
[
https://issues.apache.org/jira/browse/SPARK-9584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula closed SPARK-9584.
---
Resolution: Duplicate
HiveHBaseTableInputFormat can'be cached
---
[
https://issues.apache.org/jira/browse/SPARK-10147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula closed SPARK-10147.
Resolution: Not A Problem
App shouldn't show in HistoryServer web when the event file has been deleted
[
https://issues.apache.org/jira/browse/SPARK-10147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-10147:
-
Description:
Phenomenon：App still shows in HistoryServer web when the event file has been
deleted on
[
https://issues.apache.org/jira/browse/SPARK-10147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-10147:
-
Summary: App shouldn't show in HistoryServer web when the event file has
been deleted on hdfs (was: App
meiyoula created SPARK-10147:
Summary: App still shows in HistoryServer web when the event file
has been deleted on hdfs
Key: SPARK-10147
URL: https://issues.apache.org/jira/browse/SPARK-10147
Project:
[
https://issues.apache.org/jira/browse/SPARK-10147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-10147:
-
Description:
It is because *log-replay-executor* thread and *clean log* thread both will
write value
[
https://issues.apache.org/jira/browse/SPARK-8366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-8366:
Summary: maxNumExecutorsNeeded should properly handle failed tasks (was:
When task fails and append a new
meiyoula created SPARK-9584:
---
Summary: HiveHBaseTableInputFormat can'be cached
Key: SPARK-9584
URL: https://issues.apache.org/jira/browse/SPARK-9584
Project: Spark
Issue Type: Bug
meiyoula created SPARK-9585:
---
Summary: HiveHBaseTableInputFormat can'be cached
Key: SPARK-9585
URL: https://issues.apache.org/jira/browse/SPARK-9585
Project: Spark
Issue Type: Bug
meiyoula created SPARK-9276:
---
Summary: ThriftServer process can't stop if using command yarn
application -kill appid
Key: SPARK-9276
URL: https://issues.apache.org/jira/browse/SPARK-9276
Project: Spark
meiyoula created SPARK-9063:
---
Summary: The UI and DynamicAllocation will be wrong when event
number 1
Key: SPARK-9063
URL: https://issues.apache.org/jira/browse/SPARK-9063
Project: Spark
meiyoula created SPARK-8953:
---
Summary: SPARK_EXECUTOR_CORES has no effect to dynamic executor
allocation function
Key: SPARK-8953
URL: https://issues.apache.org/jira/browse/SPARK-8953
Project: Spark
[
https://issues.apache.org/jira/browse/SPARK-8366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-8366:
Description:
I use the *dynamic executor allocation* function.
When an executor is killed, all running
[
https://issues.apache.org/jira/browse/SPARK-8366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-8366:
Description:
I use the *dynamic executor allocation* function.
When an executor is killed, all running
[
https://issues.apache.org/jira/browse/SPARK-8366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-8366:
Description:
I use the *dynamic executor allocation* function.
When an executor is killed, all running
[
https://issues.apache.org/jira/browse/SPARK-8618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula closed SPARK-8618.
---
Resolution: Invalid
Obtain hbase token retries many times when having hbase class but no hbase
[
https://issues.apache.org/jira/browse/SPARK-8366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-8366:
Description: I use the *dynamic executor allocation* function. Then one
executor is killed, all running
[
https://issues.apache.org/jira/browse/SPARK-8560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14604582#comment-14604582
]
meiyoula commented on SPARK-8560:
-
Sorry, I think you misunderstand what I described. It's
meiyoula created SPARK-8618:
---
Summary: Obtain hbase token retries many times when having hbase
class but no hbase configuration
Key: SPARK-8618
URL: https://issues.apache.org/jira/browse/SPARK-8618
meiyoula created SPARK-8560:
---
Summary: The Executors page will have negative if having
resubmitted tasks
Key: SPARK-8560
URL: https://issues.apache.org/jira/browse/SPARK-8560
Project: Spark
Issue
[
https://issues.apache.org/jira/browse/SPARK-8560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-8560:
Attachment: screenshot-1.png
The Executors page will have negative if having resubmitted tasks
[
https://issues.apache.org/jira/browse/SPARK-7889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14591141#comment-14591141
]
meiyoula commented on SPARK-7889:
-
[~ste...@apache.org] Can you realize your proposal with
meiyoula created SPARK-8391:
---
Summary: showDagViz throws OutOfMemoryError, and the whole jobPage
throws ERROR
Key: SPARK-8391
URL: https://issues.apache.org/jira/browse/SPARK-8391
Project: Spark
[
https://issues.apache.org/jira/browse/SPARK-8391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-8391:
Summary: showDagViz throws OutOfMemoryError, and the whole jobPage is down
(was: showDagViz throws
[
https://issues.apache.org/jira/browse/SPARK-8391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-8391:
Summary: showDagViz throws OutOfMemoryError, cause the whole jobPage is
down (was: showDagViz throws
[
https://issues.apache.org/jira/browse/SPARK-8391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-8391:
Summary: showDagViz throws OutOfMemoryError, cause the whole jobPage dies
(was: showDagViz throws
[
https://issues.apache.org/jira/browse/SPARK-8391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-8391:
Description:
When the job is big, and has so many DAG nodes and edges.showDagViz throws
ERROR, then the
meiyoula created SPARK-8392:
---
Summary: the process is hang on when getting cachedNodes
Key: SPARK-8392
URL: https://issues.apache.org/jira/browse/SPARK-8392
Project: Spark
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SPARK-8392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-8392:
Issue Type: Improvement (was: Bug)
the process is hang on when getting cachedNodes
[
https://issues.apache.org/jira/browse/SPARK-8391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14587711#comment-14587711
]
meiyoula commented on SPARK-8391:
-
Is anyone has good idea on this? Look forward to your
[
https://issues.apache.org/jira/browse/SPARK-8392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-8392:
Description:
def getAllNodes: Seq[RDDOperationNode] = {
_childNodes ++
meiyoula created SPARK-8366:
---
Summary: When task fails and append a new one, the
ExecutorAllocationManager can't sense the new tasks
Key: SPARK-8366
URL: https://issues.apache.org/jira/browse/SPARK-8366
[
https://issues.apache.org/jira/browse/SPARK-8099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-8099:
Description: While testing dynamic executor allocation function, I set the
executor cores with
[
https://issues.apache.org/jira/browse/SPARK-8099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
meiyoula updated SPARK-8099:
Description: While testing dynamic executor allocation function, I set the
executor cores with
meiyoula created SPARK-8099:
---
Summary: In yarn-cluster mode, --executor-cores can't be setted
into SparkConf
Key: SPARK-8099
URL: https://issues.apache.org/jira/browse/SPARK-8099
Project: Spark
1 - 100 of 170 matches
Mail list logo
