[jira] [Comment Edited] (SPARK-26836) Columns get switched in Spark SQL using Avro backed Hive table if schema evolves

[ https://issues.apache.org/jira/browse/SPARK-26836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17261398#comment-17261398 ] Attila Zsolt Piros edited comment on SPARK-26836 at 1/8/21, 4:15 PM: -

[jira] [Commented] (SPARK-26836) Columns get switched in Spark SQL using Avro backed Hive table if schema evolves

[ https://issues.apache.org/jira/browse/SPARK-26836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17261398#comment-17261398 ] Attila Zsolt Piros commented on SPARK-26836: I am working on a this > Columns get switched

[jira] [Commented] (SPARK-32617) Upgrade kubernetes client version to support latest minikube version.

[ https://issues.apache.org/jira/browse/SPARK-32617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17248168#comment-17248168 ] Attila Zsolt Piros commented on SPARK-32617: I will have PR for this soon. > Upgrade

[jira] [Comment Edited] (SPARK-33711) Race condition in Spark k8s Pod lifecycle manager that leads to shutdowns

[ https://issues.apache.org/jira/browse/SPARK-33711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246092#comment-17246092 ] Attila Zsolt Piros edited comment on SPARK-33711 at 12/8/20, 7:21 PM:

[jira] [Commented] (SPARK-33711) Race condition in Spark k8s Pod lifecycle manager that leads to shutdowns

[ https://issues.apache.org/jira/browse/SPARK-33711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17246092#comment-17246092 ] Attila Zsolt Piros commented on SPARK-33711: Yes, it does. I have updated the affected

[jira] [Updated] (SPARK-33711) Race condition in Spark k8s Pod lifecycle manager that leads to shutdowns

[ https://issues.apache.org/jira/browse/SPARK-33711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Zsolt Piros updated SPARK-33711: --- Affects Version/s: 2.3.4 > Race condition in Spark k8s Pod lifecycle manager that

[jira] [Updated] (SPARK-33711) Race condition in Spark k8s Pod lifecycle manager that leads to shutdowns

[ https://issues.apache.org/jira/browse/SPARK-33711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Zsolt Piros updated SPARK-33711: --- Affects Version/s: (was: 3.0.1) 3.2.0

[jira] [Updated] (SPARK-33711) Race condition in Spark k8s Pod lifecycle manager that leads to shutdowns

[ https://issues.apache.org/jira/browse/SPARK-33711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Zsolt Piros updated SPARK-33711: --- Summary: Race condition in Spark k8s Pod lifecycle manager that leads to shutdowns

[jira] [Commented] (SPARK-33711) Race condition in Spark k8s Pod lifecycle management that leads to shutdowns

[ https://issues.apache.org/jira/browse/SPARK-33711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17245993#comment-17245993 ] Attila Zsolt Piros commented on SPARK-33711: I am working on this and soon I will open a PR.

[jira] [Created] (SPARK-33711) Race condition in Spark k8s Pod lifecycle management that leads to shutdowns

Attila Zsolt Piros created SPARK-33711: -- Summary: Race condition in Spark k8s Pod lifecycle management that leads to shutdowns Key: SPARK-33711 URL: https://issues.apache.org/jira/browse/SPARK-33711

[jira] [Comment Edited] (SPARK-28210) Shuffle Storage API: Reads

[ https://issues.apache.org/jira/browse/SPARK-28210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17196013#comment-17196013 ] Attila Zsolt Piros edited comment on SPARK-28210 at 9/15/20, 9:38 AM:

[jira] [Commented] (SPARK-28210) Shuffle Storage API: Reads

[ https://issues.apache.org/jira/browse/SPARK-28210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17196013#comment-17196013 ] Attila Zsolt Piros commented on SPARK-28210: [~tianczha] [~devaraj] I would like to work on

[jira] [Commented] (SPARK-32663) TransportClient getting closed when there are outstanding requests to the server

[ https://issues.apache.org/jira/browse/SPARK-32663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17181138#comment-17181138 ] Attila Zsolt Piros commented on SPARK-32663: You are right. The clients will be closed via

[jira] [Updated] (SPARK-32293) Inconsistent default unit between Spark memory configs and JVM option

[ https://issues.apache.org/jira/browse/SPARK-32293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Zsolt Piros updated SPARK-32293: --- Target Version/s: 3.1.0 > Inconsistent default unit between Spark memory configs

[jira] [Updated] (SPARK-32293) Inconsistent default unit between Spark memory configs and JVM option

[ https://issues.apache.org/jira/browse/SPARK-32293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Zsolt Piros updated SPARK-32293: --- Summary: Inconsistent default unit between Spark memory configs and JVM option

[jira] [Commented] (SPARK-32293) Inconsistent default units for configuring Spark memory

[ https://issues.apache.org/jira/browse/SPARK-32293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17156884#comment-17156884 ] Attila Zsolt Piros commented on SPARK-32293: I am working on this. > Inconsistent default

[jira] [Created] (SPARK-32293) Inconsistent default units for configuring Spark memory

Attila Zsolt Piros created SPARK-32293: -- Summary: Inconsistent default units for configuring Spark memory Key: SPARK-32293 URL: https://issues.apache.org/jira/browse/SPARK-32293 Project: Spark

[jira] [Updated] (SPARK-32149) Improve file path name normalisation at block resolution within the external shuffle service

[ https://issues.apache.org/jira/browse/SPARK-32149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Zsolt Piros updated SPARK-32149: --- Affects Version/s: (was: 3.0.1) 3.1.0 > Improve file

[jira] [Commented] (SPARK-32149) Improve file path name normalisation at block resolution within the external shuffle service

[ https://issues.apache.org/jira/browse/SPARK-32149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17149440#comment-17149440 ] Attila Zsolt Piros commented on SPARK-32149: I am working on this > Improve file path name

[jira] [Created] (SPARK-32149) Improve file path name normalisation at block resolution within the external shuffle service

Attila Zsolt Piros created SPARK-32149: -- Summary: Improve file path name normalisation at block resolution within the external shuffle service Key: SPARK-32149 URL:

[jira] [Commented] (SPARK-27651) Avoid the network when block manager fetches shuffle blocks from the same host

[ https://issues.apache.org/jira/browse/SPARK-27651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052348#comment-17052348 ] Attila Zsolt Piros commented on SPARK-27651: well in case of dynamic allocation and a

[jira] [Updated] (SPARK-27651) Avoid the network when block manager fetches shuffle blocks from the same host

[ https://issues.apache.org/jira/browse/SPARK-27651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Zsolt Piros updated SPARK-27651: --- Description: When a shuffle block (content) is fetched the network is always used

[jira] [Commented] (SPARK-27651) Avoid the network when block manager fetches shuffle blocks from the same host

[ https://issues.apache.org/jira/browse/SPARK-27651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17051995#comment-17051995 ] Attila Zsolt Piros commented on SPARK-27651: Yes, the final implementation works only when

[jira] [Comment Edited] (SPARK-30688) Spark SQL Unix Timestamp produces incorrect result with unix_timestamp UDF

[ https://issues.apache.org/jira/browse/SPARK-30688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031614#comment-17031614 ] Attila Zsolt Piros edited comment on SPARK-30688 at 2/6/20 2:22 PM:

[jira] [Commented] (SPARK-30688) Spark SQL Unix Timestamp produces incorrect result with unix_timestamp UDF

[ https://issues.apache.org/jira/browse/SPARK-30688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031614#comment-17031614 ] Attila Zsolt Piros commented on SPARK-30688: I have checked on Spark 3.0.0-preview2 and week

[jira] [Commented] (SPARK-27021) Leaking Netty event loop group for shuffle chunk fetch requests

[ https://issues.apache.org/jira/browse/SPARK-27021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16996571#comment-16996571 ] Attila Zsolt Piros commented on SPARK-27021: [~roncenzhao] it seems to me you bumped into 

[jira] [Commented] (SPARK-27021) Leaking Netty event loop group for shuffle chunk fetch requests

[ https://issues.apache.org/jira/browse/SPARK-27021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16995538#comment-16995538 ] Attila Zsolt Piros commented on SPARK-27021: [~roncenzhao] # yes # I do not think so. This

[jira] [Created] (SPARK-30235) Keeping compatibility with 2.4 external shuffle service regarding host local shuffle blocks reading

Attila Zsolt Piros created SPARK-30235: -- Summary: Keeping compatibility with 2.4 external shuffle service regarding host local shuffle blocks reading Key: SPARK-30235 URL:

[jira] [Commented] (SPARK-30235) Keeping compatibility with 2.4 external shuffle service regarding host local shuffle blocks reading

[ https://issues.apache.org/jira/browse/SPARK-30235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16994672#comment-16994672 ] Attila Zsolt Piros commented on SPARK-30235: I am working on this. > Keeping compatibility

[jira] [Commented] (SPARK-27819) Retry cleanup of disk persisted RDD via external shuffle service when it failed via executor

[ https://issues.apache.org/jira/browse/SPARK-27819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1684#comment-1684 ] Attila Zsolt Piros commented on SPARK-27819: I am working on this. > Retry cleanup of disk

[jira] [Updated] (SPARK-27819) Retry cleanup of disk persisted RDD via external shuffle service when it failed via executor

[ https://issues.apache.org/jira/browse/SPARK-27819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Zsolt Piros updated SPARK-27819: --- Description: This issue is created for not losing the idea came up during

[jira] [Created] (SPARK-27819) Retry cleanup of disk persisted RDD via external shuffle service when it failed via executor

Attila Zsolt Piros created SPARK-27819: -- Summary: Retry cleanup of disk persisted RDD via external shuffle service when it failed via executor Key: SPARK-27819 URL:

[jira] [Commented] (SPARK-27651) Avoid the network when block manager fetches shuffle blocks from the same host

[ https://issues.apache.org/jira/browse/SPARK-27651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834832#comment-16834832 ] Attila Zsolt Piros commented on SPARK-27651: I am already working on this. > Avoid the

[jira] [Created] (SPARK-27651) Avoid the network when block manager fetches shuffle blocks from the same host

Attila Zsolt Piros created SPARK-27651: -- Summary: Avoid the network when block manager fetches shuffle blocks from the same host Key: SPARK-27651 URL: https://issues.apache.org/jira/browse/SPARK-27651

[jira] [Updated] (SPARK-27622) Avoid network communication when block manager fetches disk persisted RDD blocks from the same host

[ https://issues.apache.org/jira/browse/SPARK-27622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Zsolt Piros updated SPARK-27622: --- Summary: Avoid network communication when block manager fetches disk persisted RDD

[jira] [Updated] (SPARK-27622) Avoid the network when block manager fetches disk persisted RDD blocks from the same host

[ https://issues.apache.org/jira/browse/SPARK-27622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Zsolt Piros updated SPARK-27622: --- Summary: Avoid the network when block manager fetches disk persisted RDD blocks

[jira] [Comment Edited] (SPARK-27622) Avoid network communication when block manger fetches from the same host

[ https://issues.apache.org/jira/browse/SPARK-27622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16831553#comment-16831553 ] Attila Zsolt Piros edited comment on SPARK-27622 at 5/6/19 6:22 PM:

[jira] [Updated] (SPARK-27622) Avoid network communication when block manger fetches from the same host

[ https://issues.apache.org/jira/browse/SPARK-27622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Zsolt Piros updated SPARK-27622: --- Summary: Avoid network communication when block manger fetches from the same host

[jira] [Updated] (SPARK-27622) Avoiding network communication when block manger fetching from the same host

[ https://issues.apache.org/jira/browse/SPARK-27622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Zsolt Piros updated SPARK-27622: --- Summary: Avoiding network communication when block manger fetching from the same

[jira] [Updated] (SPARK-27622) Avoiding network communication when block mangers are running on the same host

[ https://issues.apache.org/jira/browse/SPARK-27622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Zsolt Piros updated SPARK-27622: --- Summary: Avoiding network communication when block mangers are running on the same

[jira] [Commented] (SPARK-27622) Avoiding network communication when block mangers are running on the host

[ https://issues.apache.org/jira/browse/SPARK-27622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16831553#comment-16831553 ] Attila Zsolt Piros commented on SPARK-27622: I am already working on this. A working

[jira] [Created] (SPARK-27622) Avoiding network communication when block mangers are running on the host

Attila Zsolt Piros created SPARK-27622: -- Summary: Avoiding network communication when block mangers are running on the host Key: SPARK-27622 URL: https://issues.apache.org/jira/browse/SPARK-27622

[jira] [Commented] (SPARK-25888) Service requests for persist() blocks via external service after dynamic deallocation

[ https://issues.apache.org/jira/browse/SPARK-25888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16825248#comment-16825248 ] Attila Zsolt Piros commented on SPARK-25888: I am working on this. > Service requests for

[jira] [Commented] (SPARK-27090) Deplementing old LEGACY_DRIVER_IDENTIFIER ("")

[ https://issues.apache.org/jira/browse/SPARK-27090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16787822#comment-16787822 ] Attila Zsolt Piros commented on SPARK-27090: I would have waited a little bit to find out

[jira] [Created] (SPARK-27090) Deplementing old LEGACY_DRIVER_IDENTIFIER ("")

Attila Zsolt Piros created SPARK-27090: -- Summary: Deplementing old LEGACY_DRIVER_IDENTIFIER ("") Key: SPARK-27090 URL: https://issues.apache.org/jira/browse/SPARK-27090 Project: Spark

[jira] [Updated] (SPARK-27021) Netty related thread leaks ()

[ https://issues.apache.org/jira/browse/SPARK-27021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Zsolt Piros updated SPARK-27021: --- Summary: Netty related thread leaks () (was: Netty related thread leaks) > Netty

[jira] [Updated] (SPARK-27021) Leaking Netty event loop group for shuffle chunk fetch requests

[ https://issues.apache.org/jira/browse/SPARK-27021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Zsolt Piros updated SPARK-27021: --- Summary: Leaking Netty event loop group for shuffle chunk fetch requests (was:

[jira] [Updated] (SPARK-27021) Netty related thread leaks (event loop group for shuffle chunk fetch requests)

[ https://issues.apache.org/jira/browse/SPARK-27021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Zsolt Piros updated SPARK-27021: --- Summary: Netty related thread leaks (event loop group for shuffle chunk fetch

[jira] [Created] (SPARK-27021) Netty related thread leaks

Attila Zsolt Piros created SPARK-27021: -- Summary: Netty related thread leaks Key: SPARK-27021 URL: https://issues.apache.org/jira/browse/SPARK-27021 Project: Spark Issue Type: Bug

[jira] [Commented] (SPARK-27021) Netty related thread leaks

[ https://issues.apache.org/jira/browse/SPARK-27021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16781707#comment-16781707 ] Attila Zsolt Piros commented on SPARK-27021: I am already working on it. > Netty related

[jira] [Commented] (SPARK-26891) Flaky test:YarnSchedulerBackendSuite."RequestExecutors reflects node blacklist and is serializable"

[ https://issues.apache.org/jira/browse/SPARK-26891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769323#comment-16769323 ] Attila Zsolt Piros commented on SPARK-26891: I am woking on it. > Flaky

[jira] [Updated] (SPARK-26891) Flaky test:YarnSchedulerBackendSuite."RequestExecutors reflects node blacklist and is serializable"

[ https://issues.apache.org/jira/browse/SPARK-26891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Zsolt Piros updated SPARK-26891: --- Description: For even an unrelated change sometimes the

[jira] [Created] (SPARK-26891) Flaky test:YarnSchedulerBackendSuite."RequestExecutors reflects node blacklist and is serializable"

Attila Zsolt Piros created SPARK-26891: -- Summary: Flaky test:YarnSchedulerBackendSuite."RequestExecutors reflects node blacklist and is serializable" Key: SPARK-26891 URL:

[jira] [Commented] (SPARK-26845) Avro to_avro from_avro roundtrip fails if data type is string

[ https://issues.apache.org/jira/browse/SPARK-26845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16763094#comment-16763094 ] Attila Zsolt Piros commented on SPARK-26845: This also works: {code} test("roundtrip in

[jira] [Commented] (SPARK-26845) Avro to_avro from_avro roundtrip fails if data type is string

[ https://issues.apache.org/jira/browse/SPARK-26845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16763066#comment-16763066 ] Attila Zsolt Piros commented on SPARK-26845: The test would work if you replace the line

[jira] [Commented] (SPARK-25035) Replicating disk-stored blocks should avoid memory mapping

[ https://issues.apache.org/jira/browse/SPARK-25035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16755322#comment-16755322 ] Attila Zsolt Piros commented on SPARK-25035: I am working on this. > Replicating

[jira] [Commented] (SPARK-26688) Provide configuration of initially blacklisted YARN nodes

[ https://issues.apache.org/jira/browse/SPARK-26688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748922#comment-16748922 ] Attila Zsolt Piros commented on SPARK-26688: As I know a node only could have one label. So

[jira] [Updated] (SPARK-26688) Provide configuration of initially blacklisted YARN nodes

[ https://issues.apache.org/jira/browse/SPARK-26688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Zsolt Piros updated SPARK-26688: --- Description: Introducing new config for initially blacklisted YARN nodes. This

[jira] [Created] (SPARK-26688) Provide configuration of initially blacklisted YARN nodes

Attila Zsolt Piros created SPARK-26688: -- Summary: Provide configuration of initially blacklisted YARN nodes Key: SPARK-26688 URL: https://issues.apache.org/jira/browse/SPARK-26688 Project: Spark

[jira] [Commented] (SPARK-26688) Provide configuration of initially blacklisted YARN nodes

[ https://issues.apache.org/jira/browse/SPARK-26688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748632#comment-16748632 ] Attila Zsolt Piros commented on SPARK-26688: I am working on this. > Provide configuration

[jira] [Commented] (SPARK-26615) Fixing transport server/client resource leaks in the core unittests

[ https://issues.apache.org/jira/browse/SPARK-26615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742243#comment-16742243 ] Attila Zsolt Piros commented on SPARK-26615: I am working on it (soon a PR will be created)

[jira] [Updated] (SPARK-26615) Fixing transport server/client resource leaks in the core unittests

[ https://issues.apache.org/jira/browse/SPARK-26615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Zsolt Piros updated SPARK-26615: --- Affects Version/s: 3.0.0 > Fixing transport server/client resource leaks in the

[jira] [Created] (SPARK-26615) Fixing transport server/client resource leaks in the core unittests

Attila Zsolt Piros created SPARK-26615: -- Summary: Fixing transport server/client resource leaks in the core unittests Key: SPARK-26615 URL: https://issues.apache.org/jira/browse/SPARK-26615

[jira] [Commented] (SPARK-24920) Spark should allow sharing netty's memory pools across all uses

[ https://issues.apache.org/jira/browse/SPARK-24920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715040#comment-16715040 ] Attila Zsolt Piros commented on SPARK-24920: I started to work on it. I would keep a

[jira] [Comment Edited] (SPARK-24920) Spark should allow sharing netty's memory pools across all uses

[ https://issues.apache.org/jira/browse/SPARK-24920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715040#comment-16715040 ] Attila Zsolt Piros edited comment on SPARK-24920 at 12/10/18 4:39 PM:

[jira] [Resolved] (SPARK-26232) Remove old Netty3 dependency from the build

[ https://issues.apache.org/jira/browse/SPARK-26232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Zsolt Piros resolved SPARK-26232. Resolution: Won't Fix One of the third party tool uses Netty3, so as a transitive

[jira] [Updated] (SPARK-26232) Remove old Netty3 dependency from the build

[ https://issues.apache.org/jira/browse/SPARK-26232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Zsolt Piros updated SPARK-26232: --- Summary: Remove old Netty3 dependency from the build (was: Remove old Netty3

[jira] [Created] (SPARK-26232) Remove old Netty3 artifact from the build

Attila Zsolt Piros created SPARK-26232: -- Summary: Remove old Netty3 artifact from the build Key: SPARK-26232 URL: https://issues.apache.org/jira/browse/SPARK-26232 Project: Spark Issue

[jira] [Updated] (SPARK-26118) Make Jetty's requestHeaderSize configurable in Spark

[ https://issues.apache.org/jira/browse/SPARK-26118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Zsolt Piros updated SPARK-26118: --- Issue Type: New Feature (was: Bug) > Make Jetty's requestHeaderSize configurable

[jira] [Updated] (SPARK-26118) Make Jetty's requestHeaderSize configurable in Spark

[ https://issues.apache.org/jira/browse/SPARK-26118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Zsolt Piros updated SPARK-26118: --- Issue Type: Bug (was: Improvement) > Make Jetty's requestHeaderSize configurable

[jira] [Commented] (SPARK-26118) Make Jetty's requestHeaderSize configurable in Spark

[ https://issues.apache.org/jira/browse/SPARK-26118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692018#comment-16692018 ] Attila Zsolt Piros commented on SPARK-26118: I am working on a PR. > Make Jetty's

[jira] [Updated] (SPARK-26118) Make Jetty's requestHeaderSize configurable in Spark

[ https://issues.apache.org/jira/browse/SPARK-26118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Zsolt Piros updated SPARK-26118: --- Affects Version/s: (was: 2.3.2) (was: 2.4.0)

[jira] [Created] (SPARK-26118) Make Jetty's requestHeaderSize configurable in Spark

Attila Zsolt Piros created SPARK-26118: -- Summary: Make Jetty's requestHeaderSize configurable in Spark Key: SPARK-26118 URL: https://issues.apache.org/jira/browse/SPARK-26118 Project: Spark

[jira] [Commented] (SPARK-26002) SQL date operators calculates with incorrect dayOfYears for dates before 1500-03-01

[ https://issues.apache.org/jira/browse/SPARK-26002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16682404#comment-16682404 ] Attila Zsolt Piros commented on SPARK-26002: I am already working on a fix. > SQL date

[jira] [Created] (SPARK-26002) SQL date operators calculates with incorrect dayOfYears for dates before 1500-03-01

Attila Zsolt Piros created SPARK-26002: -- Summary: SQL date operators calculates with incorrect dayOfYears for dates before 1500-03-01 Key: SPARK-26002 URL: https://issues.apache.org/jira/browse/SPARK-26002

[jira] [Commented] (SPARK-24578) Reading remote cache block behavior changes and causes timeout issue

[ https://issues.apache.org/jira/browse/SPARK-24578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517515#comment-16517515 ] Attila Zsolt Piros commented on SPARK-24578: [~wbzhao] oh sorry I read your comment late,

[jira] [Commented] (SPARK-24578) Reading remote cache block behavior changes and causes timeout issue

[ https://issues.apache.org/jira/browse/SPARK-24578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517452#comment-16517452 ] Attila Zsolt Piros commented on SPARK-24578: [~wbzhao] Yes, you are right, readerIndex is

[jira] [Commented] (SPARK-24578) Reading remote cache block behavior changes and causes timeout issue

[ https://issues.apache.org/jira/browse/SPARK-24578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517416#comment-16517416 ] Attila Zsolt Piros commented on SPARK-24578: I have written a small test I know it is a bit 

[jira] [Commented] (SPARK-24578) Reading remote cache block behavior changes and causes timeout issue

[ https://issues.apache.org/jira/browse/SPARK-24578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517287#comment-16517287 ] Attila Zsolt Piros commented on SPARK-24578: The copyByteBuf() along with transferTo() is

[jira] [Commented] (SPARK-24594) Introduce metrics for YARN executor allocation problems

[ https://issues.apache.org/jira/browse/SPARK-24594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517028#comment-16517028 ] Attila Zsolt Piros commented on SPARK-24594: I am working on this. > Introduce metrics for

[jira] [Updated] (SPARK-24594) Introduce metrics for YARN executor allocation problems

[ https://issues.apache.org/jira/browse/SPARK-24594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Zsolt Piros updated SPARK-24594: --- Description: Within SPARK-16630 it come up to introduce metrics for YARN executor

[jira] [Created] (SPARK-24594) Introduce metrics for YARN executor allocation problems

Attila Zsolt Piros created SPARK-24594: -- Summary: Introduce metrics for YARN executor allocation problems Key: SPARK-24594 URL: https://issues.apache.org/jira/browse/SPARK-24594 Project: Spark

[jira] [Commented] (SPARK-19526) Spark should raise an exception when it tries to read a Hive view but it doesn't have read access on the corresponding table(s)

[ https://issues.apache.org/jira/browse/SPARK-19526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16504827#comment-16504827 ] Attila Zsolt Piros commented on SPARK-19526: I started working on this issue. > Spark

[jira] [Commented] (SPARK-19181) SparkListenerSuite.local metrics fails when average executorDeserializeTime is too short.

[ https://issues.apache.org/jira/browse/SPARK-19181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467137#comment-16467137 ] Attila Zsolt Piros commented on SPARK-19181: I am working on this. >

[jira] [Commented] (SPARK-16630) Blacklist a node if executors won't launch on it.

[ https://issues.apache.org/jira/browse/SPARK-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16432495#comment-16432495 ] Attila Zsolt Piros commented on SPARK-16630: Let me illustrate my problem with an example: -

[jira] [Commented] (SPARK-16630) Blacklist a node if executors won't launch on it.

[ https://issues.apache.org/jira/browse/SPARK-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16432415#comment-16432415 ] Attila Zsolt Piros commented on SPARK-16630: I would need the expiry times to choose the most

[jira] [Comment Edited] (SPARK-16630) Blacklist a node if executors won't launch on it.

[ https://issues.apache.org/jira/browse/SPARK-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16432165#comment-16432165 ] Attila Zsolt Piros edited comment on SPARK-16630 at 4/10/18 12:15 PM:

[jira] [Commented] (SPARK-16630) Blacklist a node if executors won't launch on it.

[ https://issues.apache.org/jira/browse/SPARK-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16432165#comment-16432165 ] Attila Zsolt Piros commented on SPARK-16630: I have question regarding limiting the number of

[jira] [Commented] (SPARK-16630) Blacklist a node if executors won't launch on it.

[ https://issues.apache.org/jira/browse/SPARK-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428721#comment-16428721 ] Attila Zsolt Piros commented on SPARK-16630: Yes you are right more executors can be

[jira] [Commented] (SPARK-16630) Blacklist a node if executors won't launch on it.

[ https://issues.apache.org/jira/browse/SPARK-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427181#comment-16427181 ] Attila Zsolt Piros commented on SPARK-16630: [~tgraves] what about stopping YARN backlisting

[jira] [Commented] (SPARK-16630) Blacklist a node if executors won't launch on it.

[ https://issues.apache.org/jira/browse/SPARK-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427123#comment-16427123 ] Attila Zsolt Piros commented on SPARK-16630: [~irashid] I would reuse

[jira] [Updated] (SPARK-23728) ML test with expected exceptions testing streaming fails on 2.3

[ https://issues.apache.org/jira/browse/SPARK-23728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Zsolt Piros updated SPARK-23728: --- Summary: ML test with expected exceptions testing streaming fails on 2.3 (was: ML

[jira] [Created] (SPARK-23728) ML test with expected exceptions via streaming fails on 2.3

Attila Zsolt Piros created SPARK-23728: -- Summary: ML test with expected exceptions via streaming fails on 2.3 Key: SPARK-23728 URL: https://issues.apache.org/jira/browse/SPARK-23728 Project:

[jira] [Commented] (SPARK-23728) ML test with expected exceptions via streaming fails on 2.3

[ https://issues.apache.org/jira/browse/SPARK-23728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16403850#comment-16403850 ] Attila Zsolt Piros commented on SPARK-23728: I am soon creating a PR. > ML test with

[jira] [Commented] (SPARK-16630) Blacklist a node if executors won't launch on it.

[ https://issues.apache.org/jira/browse/SPARK-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16391649#comment-16391649 ] Attila Zsolt Piros commented on SPARK-16630: I am working on this issue. > Blacklist a node

[jira] [Commented] (SPARK-16630) Blacklist a node if executors won't launch on it.

[ https://issues.apache.org/jira/browse/SPARK-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16387071#comment-16387071 ] Attila Zsolt Piros commented on SPARK-16630: Of course we can consider

[jira] [Commented] (SPARK-16630) Blacklist a node if executors won't launch on it.

[ https://issues.apache.org/jira/browse/SPARK-16630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16386789#comment-16386789 ] Attila Zsolt Piros commented on SPARK-16630: I have checked the existing sources and I would

[jira] [Commented] (SPARK-22915) ML test for StructuredStreaming: spark.ml.feature, N-Z

[ https://issues.apache.org/jira/browse/SPARK-22915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16379056#comment-16379056 ] Attila Zsolt Piros commented on SPARK-22915: Thank you as I have already a lot of work in it.

[jira] [Commented] (SPARK-22915) ML test for StructuredStreaming: spark.ml.feature, N-Z

[ https://issues.apache.org/jira/browse/SPARK-22915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16378987#comment-16378987 ] Attila Zsolt Piros commented on SPARK-22915: I am also very close to a PR. > ML test for

[jira] [Updated] (SPARK-23413) Sorting tasks by Host / Executor ID on the Stage page does not work

[ https://issues.apache.org/jira/browse/SPARK-23413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Zsolt Piros updated SPARK-23413: --- Description: Sorting tasks by Host / Executor ID throws exceptions:  {code}

<    1   2   3   4   >