[
https://issues.apache.org/jira/browse/SPARK-23722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405181#comment-16405181
]
Sital Kedia commented on SPARK-23722:
-
Actually this is a duplicate of SPARK-21281 and the issue has
[
https://issues.apache.org/jira/browse/SPARK-23722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sital Kedia resolved SPARK-23722.
-
Resolution: Duplicate
> Add support for inserting empty map or array to table
>
Sital Kedia created SPARK-23722:
---
Summary: Add support for inserting empty map or array to table
Key: SPARK-23722
URL: https://issues.apache.org/jira/browse/SPARK-23722
Project: Spark
Issue
[
https://issues.apache.org/jira/browse/SPARK-18134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394571#comment-16394571
]
Sital Kedia commented on SPARK-18134:
-
[~hvanhovell]- What is the state of this JIRA? Do we expect to
[
https://issues.apache.org/jira/browse/SPARK-23502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16380942#comment-16380942
]
Sital Kedia commented on SPARK-23502:
-
>> what happens when you operate on {{sc}} before it's
[
https://issues.apache.org/jira/browse/SPARK-23502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16375051#comment-16375051
]
Sital Kedia commented on SPARK-23502:
-
I realized that we are printing the web url link and the
Sital Kedia created SPARK-23502:
---
Summary: Support async init of spark context during spark-shell
startup
Key: SPARK-23502
URL: https://issues.apache.org/jira/browse/SPARK-23502
Project: Spark
[
https://issues.apache.org/jira/browse/SPARK-23310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16351097#comment-16351097
]
Sital Kedia commented on SPARK-23310:
-
https://github.com/apache/spark/pull/20492
> Perf regression
[
https://issues.apache.org/jira/browse/SPARK-23310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16350875#comment-16350875
]
Sital Kedia commented on SPARK-23310:
-
[~yhuai] - Sorry about introducing the regression for TPC-DS
Sital Kedia created SPARK-22827:
---
Summary: Avoid throwing OutOfMemoryError in case of exception in
spill
Key: SPARK-22827
URL: https://issues.apache.org/jira/browse/SPARK-22827
Project: Spark
Sital Kedia created SPARK-22312:
---
Summary: Spark job stuck with no executor due to bug in Executor
Allocation Manager
Key: SPARK-22312
URL: https://issues.apache.org/jira/browse/SPARK-22312
Project:
[
https://issues.apache.org/jira/browse/SPARK-21867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16163705#comment-16163705
]
Sital Kedia commented on SPARK-21867:
-
[~rxin] - You are right, it is very tricky to get it right.
[
https://issues.apache.org/jira/browse/SPARK-21867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16146060#comment-16146060
]
Sital Kedia commented on SPARK-21867:
-
cc - [~rxin], [~joshrosen], [~sameer] - What do you think of
Sital Kedia created SPARK-21867:
---
Summary: Support async spilling in UnsafeShuffleWriter
Key: SPARK-21867
URL: https://issues.apache.org/jira/browse/SPARK-21867
Project: Spark
Issue Type:
Sital Kedia created SPARK-21834:
---
Summary: Incorrect executor request in case of dynamic allocation
Key: SPARK-21834
URL: https://issues.apache.org/jira/browse/SPARK-21834
Project: Spark
Issue
[
https://issues.apache.org/jira/browse/SPARK-21833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sital Kedia closed SPARK-21833.
---
Resolution: Duplicate
Duplicate of SPARK-20540
> CoarseGrainedSchedulerBackend leaks executors in
[
https://issues.apache.org/jira/browse/SPARK-21833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sital Kedia updated SPARK-21833:
Description:
We have seen this issue in coarse grained scheduler that in case of dynamic
executor
[
https://issues.apache.org/jira/browse/SPARK-21833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16140533#comment-16140533
]
Sital Kedia commented on SPARK-21833:
-
Actually, SPARK-20540 already addressed this issue on latest
[
https://issues.apache.org/jira/browse/SPARK-21833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sital Kedia updated SPARK-21833:
Description:
We have seen this issue in coarse grained scheduler that in case of dynamic
executor
[
https://issues.apache.org/jira/browse/SPARK-21833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sital Kedia updated SPARK-21833:
Description:
We have seen this issue in coarse grained scheduler that in case of dynamic
executor
Sital Kedia created SPARK-21833:
---
Summary: CoarseGrainedSchedulerBackend leaks executors in case of
dynamic allocation
Key: SPARK-21833
URL: https://issues.apache.org/jira/browse/SPARK-21833
Project:
[
https://issues.apache.org/jira/browse/SPARK-19112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16109784#comment-16109784
]
Sital Kedia commented on SPARK-19112:
-
[~sowen], [~tgraves] - Using zstd compression for our Spark
[
https://issues.apache.org/jira/browse/SPARK-21444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090800#comment-16090800
]
Sital Kedia commented on SPARK-21444:
-
Any idea how to fix this issue?
> Fetch failure due to node
[
https://issues.apache.org/jira/browse/SPARK-21444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16090799#comment-16090799
]
Sital Kedia commented on SPARK-21444:
-
cc - [~joshrosen]
> Fetch failure due to node reboot causes
Sital Kedia created SPARK-21444:
---
Summary: Fetch failure due to node reboot causes job failure
Key: SPARK-21444
URL: https://issues.apache.org/jira/browse/SPARK-21444
Project: Spark
Issue
Sital Kedia created SPARK-21113:
---
Summary: Support for read ahead input stream to amortize disk IO
cost in the Spill reader
Key: SPARK-21113
URL: https://issues.apache.org/jira/browse/SPARK-21113
[
https://issues.apache.org/jira/browse/SPARK-18838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16046957#comment-16046957
]
Sital Kedia commented on SPARK-18838:
-
[~joshrosen] - The PR for my change to multi-thread the event
[
https://issues.apache.org/jira/browse/SPARK-20178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030284#comment-16030284
]
Sital Kedia commented on SPARK-20178:
-
https://github.com/apache/spark/pull/18150
> Improve
[
https://issues.apache.org/jira/browse/SPARK-20178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16027036#comment-16027036
]
Sital Kedia commented on SPARK-20178:
-
>> So to get the robustness for now I'm fine with just
[
https://issues.apache.org/jira/browse/SPARK-18838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16016217#comment-16016217
]
Sital Kedia commented on SPARK-18838:
-
[~joshrosen] - >> Alternatively, we could use two queues, one
Sital Kedia created SPARK-20640:
---
Summary: Make rpc timeout and retry for shuffle registration
configurable
Key: SPARK-20640
URL: https://issues.apache.org/jira/browse/SPARK-20640
Project: Spark
[
https://issues.apache.org/jira/browse/SPARK-20178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957341#comment-15957341
]
Sital Kedia commented on SPARK-20178:
-
[~tgraves] Thanks for creating the JIRA and driving the
[
https://issues.apache.org/jira/browse/SPARK-20163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sital Kedia closed SPARK-20163.
---
Resolution: Duplicate
> Kill all running tasks in a stage in case of fetch failure
>
[
https://issues.apache.org/jira/browse/SPARK-20163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15951738#comment-15951738
]
Sital Kedia commented on SPARK-20163:
-
Thanks [~imranr], closing this as this is duplicate of
Sital Kedia created SPARK-20163:
---
Summary: Kill all running tasks in a stage in case of fetch failure
Key: SPARK-20163
URL: https://issues.apache.org/jira/browse/SPARK-20163
Project: Spark
[
https://issues.apache.org/jira/browse/SPARK-3577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15947669#comment-15947669
]
Sital Kedia commented on SPARK-3577:
I am making a change to report correct spill data size on disk.
Sital Kedia created SPARK-20091:
---
Summary: DagScheduler should allow running concurrent attempts of
a stage in case of multiple fetch failure
Key: SPARK-20091
URL: https://issues.apache.org/jira/browse/SPARK-20091
Sital Kedia created SPARK-20074:
---
Summary: Make buffer size in unsafe external sorter configurable
Key: SPARK-20074
URL: https://issues.apache.org/jira/browse/SPARK-20074
Project: Spark
Issue
[
https://issues.apache.org/jira/browse/SPARK-20014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sital Kedia updated SPARK-20014:
Description:
When the individual partition size in a spill is small,
mergeSpillsWithTransferTo
Sital Kedia created SPARK-20014:
---
Summary: Optimize mergeSpillsWithFileStream method
Key: SPARK-20014
URL: https://issues.apache.org/jira/browse/SPARK-20014
Project: Spark
Issue Type:
[
https://issues.apache.org/jira/browse/SPARK-19837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15897961#comment-15897961
]
Sital Kedia commented on SPARK-19837:
-
`SparkHiveDynamicPartitionWriterContainer` has been refactored
[
https://issues.apache.org/jira/browse/SPARK-19837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sital Kedia closed SPARK-19837.
---
Resolution: Fixed
> Fetch failure throws a SparkException in SparkHiveWriter
>
Sital Kedia created SPARK-19837:
---
Summary: Fetch failure throws a SparkException in SparkHiveWriter
Key: SPARK-19837
URL: https://issues.apache.org/jira/browse/SPARK-19837
Project: Spark
Issue
Sital Kedia created SPARK-19803:
---
Summary: Flaky BlockManagerProactiveReplicationSuite tests
Key: SPARK-19803
URL: https://issues.apache.org/jira/browse/SPARK-19803
Project: Spark
Issue Type:
Sital Kedia created SPARK-19753:
---
Summary: Remove all shuffle files on a host in case of slave lost
of fetch failure
Key: SPARK-19753
URL: https://issues.apache.org/jira/browse/SPARK-19753
Project:
[
https://issues.apache.org/jira/browse/SPARK-18838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15753535#comment-15753535
]
Sital Kedia commented on SPARK-18838:
-
cc - [~kayousterhout]
> High latency of event processing for
[
https://issues.apache.org/jira/browse/SPARK-18838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sital Kedia updated SPARK-18838:
Description:
Currently we are observing the issue of very high event processing delay in
driver's
[
https://issues.apache.org/jira/browse/SPARK-18838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15750217#comment-15750217
]
Sital Kedia commented on SPARK-18838:
-
[~zsxwing] - Its not only the ExecutorAllocationManager, other
[
https://issues.apache.org/jira/browse/SPARK-18838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sital Kedia updated SPARK-18838:
Description:
Currently we are observing the issue of very high event processing delay in
driver's
[
https://issues.apache.org/jira/browse/SPARK-18838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15744086#comment-15744086
]
Sital Kedia commented on SPARK-18838:
-
[~rxin], [~zsxwing] - Any thoughts on this?
> High latency
[
https://issues.apache.org/jira/browse/SPARK-18838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sital Kedia updated SPARK-18838:
Description:
Currently we are observing the issue of very high event processing delay in
driver's
Sital Kedia created SPARK-18838:
---
Summary: High latency of event processing for large jobs
Key: SPARK-18838
URL: https://issues.apache.org/jira/browse/SPARK-18838
Project: Spark
Issue Type:
[
https://issues.apache.org/jira/browse/SPARK-13510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15671415#comment-15671415
]
Sital Kedia commented on SPARK-13510:
-
[~shenhong] - We are seeing the same issue on our side. Do you
[
https://issues.apache.org/jira/browse/SPARK-16827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sital Kedia updated SPARK-16827:
Summary: Stop reporting spill metrics as shuffle metrics (was: Query with
Join produces excessive
[
https://issues.apache.org/jira/browse/SPARK-17839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sital Kedia updated SPARK-17839:
Summary: Use Nio's directbuffer instead of BufferedInputStream in order to
avoid additional copy
Sital Kedia created SPARK-17839:
---
Summary: UnsafeSorterSpillReader should use Nio's directbuffer to
read the spill files in order to avoid additional copy
Key: SPARK-17839
URL:
[
https://issues.apache.org/jira/browse/SPARK-17509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sital Kedia updated SPARK-17509:
Affects Version/s: 2.0.0
Description: Profiling a job, we saw that patten matching in
Sital Kedia created SPARK-17509:
---
Summary: When wrapping catalyst datatype to Hive data type avoid
pattern matching
Key: SPARK-17509
URL: https://issues.apache.org/jira/browse/SPARK-17509
Project:
[
https://issues.apache.org/jira/browse/SPARK-16922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15469092#comment-15469092
]
Sital Kedia commented on SPARK-16922:
-
There is no noticable performance gain I observed comparing to
[
https://issues.apache.org/jira/browse/SPARK-16922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15468339#comment-15468339
]
Sital Kedia commented on SPARK-16922:
-
[~davies] - Thanks for looking into this. I tested the
[
https://issues.apache.org/jira/browse/SPARK-16922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456744#comment-15456744
]
Sital Kedia commented on SPARK-16922:
-
Thanks for the fix [~davies]. I will test this change with our
[
https://issues.apache.org/jira/browse/SPARK-17164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sital Kedia closed SPARK-17164.
---
Resolution: Won't Fix
> Query with colon in the table name fails to parse in 2.0
>
[
https://issues.apache.org/jira/browse/SPARK-17164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15431031#comment-15431031
]
Sital Kedia commented on SPARK-17164:
-
Thanks [~rxin], [~hvanhovell], that makes sense. The issue is
[
https://issues.apache.org/jira/browse/SPARK-17164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429193#comment-15429193
]
Sital Kedia commented on SPARK-17164:
-
cc - [~hvanhovell], [~rxin]
> Query with colon in the table
Sital Kedia created SPARK-17164:
---
Summary: Query with colon in the table name fails to parse in 2.0
Key: SPARK-17164
URL: https://issues.apache.org/jira/browse/SPARK-17164
Project: Spark
Issue
[
https://issues.apache.org/jira/browse/SPARK-16922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427429#comment-15427429
]
Sital Kedia commented on SPARK-16922:
-
Kryo
> Query with Broadcast Hash join fails due to executor
[
https://issues.apache.org/jira/browse/SPARK-16922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427259#comment-15427259
]
Sital Kedia commented on SPARK-16922:
-
>> Could you also try to disable the dense mode?
I tried
[
https://issues.apache.org/jira/browse/SPARK-16922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427250#comment-15427250
]
Sital Kedia commented on SPARK-16922:
-
The failure is deterministic, we are reproducing the issue for
[
https://issues.apache.org/jira/browse/SPARK-17113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sital Kedia updated SPARK-17113:
Summary: Job failure due to Executor OOM in offheap mode (was: Job failure
due to Executor OOM)
[
https://issues.apache.org/jira/browse/SPARK-17113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15425216#comment-15425216
]
Sital Kedia commented on SPARK-17113:
-
cc - [~davies]
> Job failure due to Executor OOM
>
Sital Kedia created SPARK-17113:
---
Summary: Job failure due to Executor OOM
Key: SPARK-17113
URL: https://issues.apache.org/jira/browse/SPARK-17113
Project: Spark
Issue Type: Bug
Affects
[
https://issues.apache.org/jira/browse/SPARK-16922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421524#comment-15421524
]
Sital Kedia commented on SPARK-16922:
-
Yes, I have the above mentioned PR as well.
> Query with
[
https://issues.apache.org/jira/browse/SPARK-16922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419458#comment-15419458
]
Sital Kedia commented on SPARK-16922:
-
I am using the fix in
[
https://issues.apache.org/jira/browse/SPARK-16922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sital Kedia updated SPARK-16922:
Summary: Query with Broadcast Hash join fails due to executor OOM in Spark
2.0 (was: Query
[
https://issues.apache.org/jira/browse/SPARK-16922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419383#comment-15419383
]
Sital Kedia edited comment on SPARK-16922 at 8/12/16 8:06 PM:
--
I found that
[
https://issues.apache.org/jira/browse/SPARK-16922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15419383#comment-15419383
]
Sital Kedia commented on SPARK-16922:
-
I found that the regression was introduced in
[
https://issues.apache.org/jira/browse/SPARK-16922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15410703#comment-15410703
]
Sital Kedia commented on SPARK-16922:
-
Update - The query works fine when Broadcast hash join in
[
https://issues.apache.org/jira/browse/SPARK-16922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15409878#comment-15409878
]
Sital Kedia commented on SPARK-16922:
-
PS - Rerunning the query with
[
https://issues.apache.org/jira/browse/SPARK-16922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15409813#comment-15409813
]
Sital Kedia commented on SPARK-16922:
-
cc - [~rxin]
> Query failure due to executor OOM in Spark
Sital Kedia created SPARK-16922:
---
Summary: Query failure due to executor OOM in Spark 2.0
Key: SPARK-16922
URL: https://issues.apache.org/jira/browse/SPARK-16922
Project: Spark
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SPARK-16827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15402461#comment-15402461
]
Sital Kedia commented on SPARK-16827:
-
Performance is worse for this job. But I suspect this is not
[
https://issues.apache.org/jira/browse/SPARK-16827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15401523#comment-15401523
]
Sital Kedia commented on SPARK-16827:
-
Actually it seems like this is a bug in shuffle write metrics
[
https://issues.apache.org/jira/browse/SPARK-16827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15401413#comment-15401413
]
Sital Kedia edited comment on SPARK-16827 at 8/1/16 12:52 AM:
--
That is not
[
https://issues.apache.org/jira/browse/SPARK-16827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15401413#comment-15401413
]
Sital Kedia commented on SPARK-16827:
-
That is not the case. There is no broadcast join involved, its
[
https://issues.apache.org/jira/browse/SPARK-16827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sital Kedia updated SPARK-16827:
Description:
One of our hive job which looks like this -
{code}
SELECT userid
FROM table1
[
https://issues.apache.org/jira/browse/SPARK-16827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15401405#comment-15401405
]
Sital Kedia commented on SPARK-16827:
-
[~rxin] - Any idea how to debug this issue?
> Query with Join
[
https://issues.apache.org/jira/browse/SPARK-16827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sital Kedia updated SPARK-16827:
Description:
One of our hive job which looks like this -
{code}
SELECT userid
FROM table1
[
https://issues.apache.org/jira/browse/SPARK-16827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sital Kedia updated SPARK-16827:
Summary: Query with Join produces excessive amount of shuffle data (was:
Query with Join produces
[
https://issues.apache.org/jira/browse/SPARK-16827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sital Kedia updated SPARK-16827:
Description:
One of our hive job which looks like this -
{code]
SELECT userid
FROM table1
Sital Kedia created SPARK-16827:
---
Summary: Query with Join produces excessive shuffle data
Key: SPARK-16827
URL: https://issues.apache.org/jira/browse/SPARK-16827
Project: Spark
Issue Type:
Sital Kedia created SPARK-15958:
---
Summary: Make initial buffer size for the Sorter configurable
Key: SPARK-15958
URL: https://issues.apache.org/jira/browse/SPARK-15958
Project: Spark
Issue
Sital Kedia created SPARK-15569:
---
Summary: Executors spending significant time in
DiskObjectWriter.updateBytesWritten function
Key: SPARK-15569
URL: https://issues.apache.org/jira/browse/SPARK-15569
[
https://issues.apache.org/jira/browse/SPARK-15391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289791#comment-15289791
]
Sital Kedia commented on SPARK-15391:
-
cc- [~davies] - Any idea how to fix this issue?
> Spark
[
https://issues.apache.org/jira/browse/SPARK-15391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sital Kedia updated SPARK-15391:
Description:
While running a query, we are seeing a lot of executor OOM while doing TimSort.
[
https://issues.apache.org/jira/browse/SPARK-15391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sital Kedia updated SPARK-15391:
Description:
While running a query, we are seeing a lot of executor OOM while doing TimSort.
Sital Kedia created SPARK-15391:
---
Summary: Spark executor OOM during TimSort
Key: SPARK-15391
URL: https://issues.apache.org/jira/browse/SPARK-15391
Project: Spark
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SPARK-13850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15286906#comment-15286906
]
Sital Kedia commented on SPARK-13850:
-
I am not 100% sure of the root cause, but I suspect this is
[
https://issues.apache.org/jira/browse/SPARK-13850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15283110#comment-15283110
]
Sital Kedia commented on SPARK-13850:
-
I have found a workaround for this issue. Please take a look
[
https://issues.apache.org/jira/browse/SPARK-15233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sital Kedia updated SPARK-15233:
Affects Version/s: 1.6.1
Priority: Minor (was: Major)
Description:
Sital Kedia created SPARK-15233:
---
Summary: Spark UI should show metrics for hdfs read write latency
Key: SPARK-15233
URL: https://issues.apache.org/jira/browse/SPARK-15233
Project: Spark
Issue
1 - 100 of 141 matches
Mail list logo
