[jira] [Commented] (SPARK-38794) When ConfigMap creation fails, Spark driver starts but fails to start executors

2025-01-21 Thread zuotingbing (Jira)
[ https://issues.apache.org/jira/browse/SPARK-38794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17914918#comment-17914918 ] zuotingbing commented on SPARK-38794: - Is there a solution to the bug? > When Confi

[jira] (SPARK-29211) Second invocation of custom UDF results in exception (when invoked from shell)

2024-12-26 Thread zuotingbing (Jira)
[ https://issues.apache.org/jira/browse/SPARK-29211 ] zuotingbing deleted comment on SPARK-29211: - was (Author: zuo.tingbing9): I tried with 3.4.1 and see the same issue. Is there any progress? > Second invocation of custom UDF results in excep

[jira] [Updated] (SPARK-49522) when column added with '+' for many times(>30) , the driver process hangs at org.apache.spark.sql.catalyst.expressions.BinaryArithmetic.dataType

2024-12-19 Thread zuotingbing (Jira)
[ https://issues.apache.org/jira/browse/SPARK-49522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-49522: Fix Version/s: 3.5.4 3.4.4 > when column added with '+' for many times(>30) , t

[jira] [Updated] (SPARK-50610) we should fix the decimal precision on function toInspector(dataType: DataType) in HiveInspectors class

2024-12-19 Thread zuotingbing (Jira)
[ https://issues.apache.org/jira/browse/SPARK-50610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-50610: Labels: decimal (was: ) > we should fix the decimal precision on function toInspector(dataType:

[jira] [Updated] (SPARK-50610) we should fix the decimal precision on function toInspector(dataType: DataType) in HiveInspectors class

2024-12-18 Thread zuotingbing (Jira)
[ https://issues.apache.org/jira/browse/SPARK-50610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-50610: Description: When we add some mask UDF on Decimal(18,10) type coloumn in hive-sdf moudle, the sca

[jira] [Updated] (SPARK-50610) we should fix the decimal precision on function toInspector(dataType: DataType) in HiveInspectors class

2024-12-18 Thread zuotingbing (Jira)
[ https://issues.apache.org/jira/browse/SPARK-50610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-50610: Attachment: image-2024-12-19-08-54-19-895.png > we should fix the decimal precision on function to

[jira] [Updated] (SPARK-50610) we should fix the decimal precision on function toInspector(dataType: DataType) in HiveInspectors class

2024-12-18 Thread zuotingbing (Jira)
[ https://issues.apache.org/jira/browse/SPARK-50610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-50610: Attachment: (was: image-2024-12-18-17-01-08-790.png) > we should fix the decimal precision on

[jira] [Comment Edited] (SPARK-50610) we should fix the decimal precision on function toInspector(dataType: DataType) in HiveInspectors class

2024-12-18 Thread zuotingbing (Jira)
[ https://issues.apache.org/jira/browse/SPARK-50610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906659#comment-17906659 ] zuotingbing edited comment on SPARK-50610 at 12/19/24 12:49 AM: --

[jira] [Comment Edited] (SPARK-50610) we should fix the decimal precision on function toInspector(dataType: DataType) in HiveInspectors class

2024-12-18 Thread zuotingbing (Jira)
[ https://issues.apache.org/jira/browse/SPARK-50610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906659#comment-17906659 ] zuotingbing edited comment on SPARK-50610 at 12/18/24 9:20 AM: ---

[jira] [Updated] (SPARK-50610) we should fix the decimal precision on function toInspector(dataType: DataType) in HiveInspectors class

2024-12-18 Thread zuotingbing (Jira)
[ https://issues.apache.org/jira/browse/SPARK-50610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-50610: Description: when we add some mask UDF on Decimal(18,10) type coloumn in hive-sdf moudle, the sca

[jira] [Commented] (SPARK-50610) we should fix the decimal precision on function toInspector(dataType: DataType) in HiveInspectors class

2024-12-18 Thread zuotingbing (Jira)
[ https://issues.apache.org/jira/browse/SPARK-50610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906659#comment-17906659 ] zuotingbing commented on SPARK-50610: - !image-2024-12-18-17-01-08-790.png! > we sho

[jira] [Updated] (SPARK-50610) we should fix the decimal precision on function toInspector(dataType: DataType) in HiveInspectors class

2024-12-18 Thread zuotingbing (Jira)
[ https://issues.apache.org/jira/browse/SPARK-50610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-50610: Attachment: image-2024-12-18-17-01-08-790.png > we should fix the decimal precision on function to

[jira] [Created] (SPARK-50610) we should fix the decimal precision on function toInspector(dataType: DataType) in HiveInspectors class

2024-12-18 Thread zuotingbing (Jira)
zuotingbing created SPARK-50610: --- Summary: we should fix the decimal precision on function toInspector(dataType: DataType) in HiveInspectors class Key: SPARK-50610 URL: https://issues.apache.org/jira/browse/SPARK-50

[jira] [Updated] (SPARK-49522) when column added with '+' for many times , the driver process hangs at org.apache.spark.sql.catalyst.expressions.BinaryArithmetic.dataType

2024-09-05 Thread zuotingbing (Jira)
[ https://issues.apache.org/jira/browse/SPARK-49522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-49522: Description: spark-sql --master local[4] --total-executor-cores 1 --executor-cores 3 --executor-m

[jira] [Updated] (SPARK-49522) when column added with '+' for many times(>30) , the driver process hangs at org.apache.spark.sql.catalyst.expressions.BinaryArithmetic.dataType

2024-09-05 Thread zuotingbing (Jira)
[ https://issues.apache.org/jira/browse/SPARK-49522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-49522: Summary: when column added with '+' for many times(>30) , the driver process hangs at org.apache.

[jira] [Updated] (SPARK-49522) when column added with '+' for many times , the driver process hangs at org.apache.spark.sql.catalyst.expressions.BinaryArithmetic.dataType

2024-09-05 Thread zuotingbing (Jira)
[ https://issues.apache.org/jira/browse/SPARK-49522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-49522: Summary: when column added with '+' for many times , the driver process hangs at org.apache.spark.

[jira] [Updated] (SPARK-49522) when udf added with '+' for many times , the drvier process hangs at org.apache.spark.sql.catalyst.expressions.BinaryArithmetic.dataType

2024-09-05 Thread zuotingbing (Jira)
[ https://issues.apache.org/jira/browse/SPARK-49522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-49522: Fix Version/s: 3.4.2 > when udf added with '+' for many times , the drvier process hangs at > org

[jira] [Updated] (SPARK-49522) when udf added with '+' for many times , the drvier process hangs at org.apache.spark.sql.catalyst.expressions.BinaryArithmetic.dataType

2024-09-04 Thread zuotingbing (Jira)
[ https://issues.apache.org/jira/browse/SPARK-49522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-49522: Description: spark-sql --master local[4] --total-executor-cores 1 --executor-cores 3 --executor-m

[jira] [Created] (SPARK-49522) when udf added with '+' for many times , the drvier process hangs at org.apache.spark.sql.catalyst.expressions.BinaryArithmetic.dataType

2024-09-04 Thread zuotingbing (Jira)
zuotingbing created SPARK-49522: --- Summary: when udf added with '+' for many times , the drvier process hangs at org.apache.spark.sql.catalyst.expressions.BinaryArithmetic.dataType Key: SPARK-49522 URL: https://issu

[jira] [Commented] (SPARK-38079) Not waiting for configmap before starting driver

2023-05-24 Thread zuotingbing (Jira)
[ https://issues.apache.org/jira/browse/SPARK-38079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17726030#comment-17726030 ] zuotingbing commented on SPARK-38079: - We face the same problem. Is there anybody fo

[jira] [Updated] (SPARK-28014) All waiting apps will be changed to the wrong state of Running after master changed

2019-06-12 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-28014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-28014: Summary: All waiting apps will be changed to the wrong state of Running after master changed (was

[jira] [Updated] (SPARK-28014) All waiting apps will be changed to the wrong state of Running

2019-06-12 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-28014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-28014: Description: These waiting apps which granted 0 cores will be changed to Running state after mast

[jira] [Updated] (SPARK-28014) All waiting apps will be changed to the wrong state of Running

2019-06-12 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-28014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-28014: Attachment: image-2019-06-12-15-38-45-367.png > All waiting apps will be changed to the wrong sta

[jira] [Updated] (SPARK-28014) All waiting apps will be changed to the wrong state of Running

2019-06-12 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-28014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-28014: Attachment: image-2019-06-12-15-36-14-211.png > All waiting apps will be changed to the wrong sta

[jira] [Updated] (SPARK-28014) All waiting apps will be changed to the wrong state of Running

2019-06-12 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-28014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-28014: Priority: Major (was: Minor) > All waiting apps will be changed to the wrong state of Running >

[jira] [Updated] (SPARK-28014) All waiting apps will be changed to the wrong state of Running

2019-06-12 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-28014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-28014: Description: These waiting apps which granted 0 cores will be changed to Running state, that is a

[jira] [Created] (SPARK-28014) All waiting apps will be changed to the wrong state of Running

2019-06-11 Thread zuotingbing (JIRA)
zuotingbing created SPARK-28014: --- Summary: All waiting apps will be changed to the wrong state of Running Key: SPARK-28014 URL: https://issues.apache.org/jira/browse/SPARK-28014 Project: Spark

[jira] [Comment Edited] (SPARK-23191) Workers registration failes in case of network drop

2019-05-14 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-23191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16835256#comment-16835256 ] zuotingbing edited comment on SPARK-23191 at 5/15/19 3:07 AM:

[jira] [Comment Edited] (SPARK-23191) Workers registration failes in case of network drop

2019-05-07 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-23191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16835256#comment-16835256 ] zuotingbing edited comment on SPARK-23191 at 5/8/19 2:21 AM: -

[jira] [Commented] (SPARK-23191) Workers registration failes in case of network drop

2019-05-07 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-23191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16835256#comment-16835256 ] zuotingbing commented on SPARK-23191: - See these detail logs, master changed from vm

[jira] [Comment Edited] (SPARK-23191) Workers registration failes in case of network drop

2019-04-29 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-23191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16829051#comment-16829051 ] zuotingbing edited comment on SPARK-23191 at 4/29/19 9:28 AM:

[jira] [Commented] (SPARK-23191) Workers registration failes in case of network drop

2019-04-29 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-23191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16829051#comment-16829051 ] zuotingbing commented on SPARK-23191: - we faced the same issue in standalone HA mode

[jira] [Commented] (SPARK-16190) Worker registration failed: Duplicate worker ID

2019-03-19 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-16190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796772#comment-16796772 ] zuotingbing commented on SPARK-16190: - i faced the same issue. worker log as follows

[jira] [Comment Edited] (SPARK-16190) Worker registration failed: Duplicate worker ID

2019-03-19 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-16190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796772#comment-16796772 ] zuotingbing edited comment on SPARK-16190 at 3/20/19 3:57 AM:

[jira] [Comment Edited] (SPARK-16190) Worker registration failed: Duplicate worker ID

2019-03-19 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-16190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796772#comment-16796772 ] zuotingbing edited comment on SPARK-16190 at 3/20/19 4:02 AM:

[jira] [Comment Edited] (SPARK-16190) Worker registration failed: Duplicate worker ID

2019-03-19 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-16190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796772#comment-16796772 ] zuotingbing edited comment on SPARK-16190 at 3/20/19 3:59 AM:

[jira] [Comment Edited] (SPARK-16190) Worker registration failed: Duplicate worker ID

2019-03-19 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-16190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796772#comment-16796772 ] zuotingbing edited comment on SPARK-16190 at 3/20/19 4:00 AM:

[jira] [Comment Edited] (SPARK-27010) find out the actual port number when hive.server2.thrift.port=0

2019-02-28 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16781160#comment-16781160 ] zuotingbing edited comment on SPARK-27010 at 3/1/19 1:27 AM: -

[jira] [Updated] (SPARK-27010) find out the actual port number when hive.server2.thrift.port=0

2019-02-28 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-27010: Attachment: 2019-03-01_092511.png > find out the actual port number when hive.server2.thrift.port=

[jira] [Updated] (SPARK-27010) find out the actual port number when hive.server2.thrift.port=0

2019-02-28 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-27010: Attachment: (was: 2019-03-01_090847.png) > find out the actual port number when hive.server2.t

[jira] [Commented] (SPARK-27010) find out the actual port number when hive.server2.thrift.port=0

2019-02-28 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16781160#comment-16781160 ] zuotingbing commented on SPARK-27010: - Currently, if we set *SPARK_MASTER_PORT=0*, w

[jira] [Updated] (SPARK-27010) find out the actual port number when hive.server2.thrift.port=0

2019-02-28 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-27010: Attachment: 2019-03-01_090847.png > find out the actual port number when hive.server2.thrift.port=

[jira] [Updated] (SPARK-27010) find out the actual port number when hive.server2.thrift.port=0

2019-02-28 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-27010: Description: Currently, if we set *hive.server2.thrift.port=0*, it hard to find out the actual po

[jira] [Created] (SPARK-27010) display the actual port number when hive.server2.thrift.port=0

2019-02-28 Thread zuotingbing (JIRA)
zuotingbing created SPARK-27010: --- Summary: display the actual port number when hive.server2.thrift.port=0 Key: SPARK-27010 URL: https://issues.apache.org/jira/browse/SPARK-27010 Project: Spark

[jira] [Updated] (SPARK-27010) find out the actual port number when hive.server2.thrift.port=0

2019-02-28 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-27010: Description: Currently, if we set *hive.server2.thrift.port=0*, it hard to find out the actual po

[jira] [Updated] (SPARK-27010) find out the actual port number when hive.server2.thrift.port=0

2019-02-28 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-27010: Description: Currently, if we set *hive.server2.thrift.port=0*, it hard to find out the actual po

[jira] [Updated] (SPARK-27010) find out the actual port number when hive.server2.thrift.port=0

2019-02-28 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-27010: Description: Currently, if we set *hive.server2.thrift.port=0*, it hard to find out the actual po

[jira] [Updated] (SPARK-27010) find out the actual port number when hive.server2.thrift.port=0

2019-02-28 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-27010: Attachment: 2019-02-28_170844.png > find out the actual port number when hive.server2.thrift.port=

[jira] [Updated] (SPARK-27010) find out the actual port number when hive.server2.thrift.port=0

2019-02-28 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-27010: Attachment: 2019-02-28_170904.png > find out the actual port number when hive.server2.thrift.port=

[jira] [Updated] (SPARK-27010) find out the actual port number when hive.server2.thrift.port=0

2019-02-28 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-27010: Attachment: 2019-02-28_170942.png > find out the actual port number when hive.server2.thrift.port=

[jira] [Updated] (SPARK-27010) find out the actual port number when hive.server2.thrift.port=0

2019-02-28 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-27010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-27010: Summary: find out the actual port number when hive.server2.thrift.port=0 (was: display the actual

[jira] [Updated] (SPARK-25852) we should filter the workOffers with freeCores>=CPUS_PER_TASK at first for better performance

2018-11-09 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-25852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-25852: Priority: Trivial (was: Major) > we should filter the workOffers with freeCores>=CPUS_PER_TASK at

[jira] [Updated] (SPARK-25852) we should filter the workOffers with freeCores>=CPUS_PER_TASK at first for better performance

2018-10-30 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-25852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-25852: Summary: we should filter the workOffers with freeCores>=CPUS_PER_TASK at first for better perform

[jira] [Updated] (SPARK-25852) we should filter the workOffers of which freeCores>=CPUS_PER_TASK at first for better performance

2018-10-30 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-25852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-25852: Description: We should filter the workOffers with freeCores>=CPUS_PER_TASK for better performance.

[jira] [Updated] (SPARK-25852) we should filter the workOffers of which freeCores>=CPUS_PER_TASK at first for better performance

2018-10-30 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-25852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-25852: Summary: we should filter the workOffers of which freeCores>=CPUS_PER_TASK at first for better per

[jira] [Updated] (SPARK-25852) we should filter the workOffers of which freeCores>CPUS_PER_TASK at first for better performance

2018-10-30 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-25852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-25852: Description: We should filter the workOffers of which freeCores>=CPUS_PER_TASK for better performa

[jira] [Updated] (SPARK-25852) we should filter the workOffers of which freeCores>CPUS_PER_TASK at first for better performance

2018-10-29 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-25852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-25852: Summary: we should filter the workOffers of which freeCores>CPUS_PER_TASK at first for better perf

[jira] [Updated] (SPARK-25852) we should filter the workOffers of which freeCores>0 for better performance

2018-10-26 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-25852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-25852: Priority: Major (was: Minor) > we should filter the workOffers of which freeCores>0 for better pe

[jira] [Updated] (SPARK-25852) we should filter the workOffers of which freeCores>0 for better performance

2018-10-26 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-25852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-25852: Description: We should filter the workOffers of which freeCores=0 for better performance. (was: W

[jira] [Updated] (SPARK-25852) we should filter the workOffers of which freeCores>0 for better performance

2018-10-26 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-25852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-25852: Summary: we should filter the workOffers of which freeCores>0 for better performance (was: we sho

[jira] [Updated] (SPARK-25852) we should filter the workOffers of which freeCores>0 when make fake resource offers on all executors

2018-10-26 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-25852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-25852: Component/s: (was: Spark Core) Scheduler > we should filter the workOffers of

[jira] [Updated] (SPARK-25852) we should filter the workOffers of which freeCores>0 when make fake resource offers on all executors

2018-10-26 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-25852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-25852: Attachment: 2018-10-26_162822.png > we should filter the workOffers of which freeCores>0 when make

[jira] [Updated] (SPARK-25852) we should filter the workOffers of which freeCores>0 when make fake resource offers on all executors

2018-10-26 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-25852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-25852: Summary: we should filter the workOffers of which freeCores>0 when make fake resource offers on al

[jira] [Created] (SPARK-25852) we should filter the workOffers of which freeCores=0 when make fake resource offers on all executors

2018-10-26 Thread zuotingbing (JIRA)
zuotingbing created SPARK-25852: --- Summary: we should filter the workOffers of which freeCores=0 when make fake resource offers on all executors Key: SPARK-25852 URL: https://issues.apache.org/jira/browse/SPARK-25852

[jira] [Comment Edited] (SPARK-25451) Stages page doesn't show the right number of the total tasks

2018-09-18 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-25451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16618837#comment-16618837 ] zuotingbing edited comment on SPARK-25451 at 9/18/18 10:11 AM: ---

[jira] [Updated] (SPARK-25451) Stages page doesn't show the right number of the total tasks

2018-09-18 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-25451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-25451: Target Version/s: (was: 2.3.1) > Stages page doesn't show the right number of the total tasks >

[jira] [Commented] (SPARK-25451) Stages page doesn't show the right number of the total tasks

2018-09-18 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-25451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16618837#comment-16618837 ] zuotingbing commented on SPARK-25451: - yes, thanks > Stages page doesn't show the r

[jira] [Updated] (SPARK-25451) Stages page doesn't show the right number of the total tasks

2018-09-18 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-25451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-25451: Description:   See the attached pic.   !mshot.png! The executor 1 has 7 tasks, but in the Stage

[jira] [Updated] (SPARK-25451) Stages page doesn't show the right number of the total tasks

2018-09-18 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-25451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-25451: Description:   See the attached pic.   !image-2018-09-18-16-35-09-548.png! The executor 1 has

[jira] [Updated] (SPARK-25451) Stages page doesn't show the right number of the total tasks

2018-09-18 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-25451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-25451: Attachment: mshot.png > Stages page doesn't show the right number of the total tasks > ---

[jira] [Created] (SPARK-25451) Stages page doesn't show the right number of the total tasks

2018-09-18 Thread zuotingbing (JIRA)
zuotingbing created SPARK-25451: --- Summary: Stages page doesn't show the right number of the total tasks Key: SPARK-25451 URL: https://issues.apache.org/jira/browse/SPARK-25451 Project: Spark I

[jira] [Updated] (SPARK-24829) In Spark Thrift Server, CAST AS FLOAT inconsistent with spark-shell or spark-sql

2018-07-17 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-24829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-24829: Summary: In Spark Thrift Server, CAST AS FLOAT inconsistent with spark-shell or spark-sql (was:

[jira] [Updated] (SPARK-24829) In Spark Thrift Server, CAST AS FLOAT inconsistent with spark-shell or spark-sql

2018-07-17 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-24829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-24829: Attachment: (was: CAST-FLOAT.png) > In Spark Thrift Server, CAST AS FLOAT inconsistent with sp

[jira] [Updated] (SPARK-24829) In Spark Thrift Server, CAST AS FLOAT inconsistent with spark-shell or spark-sql

2018-07-17 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-24829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-24829: Attachment: 2018-07-18_11.png > In Spark Thrift Server, CAST AS FLOAT inconsistent with spark-

[jira] [Updated] (SPARK-24829) In Spark Thrift Server, CAST AS FLOAT inconsistent with spark-shell or spark-sql

2018-07-17 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-24829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-24829: Attachment: 2018-07-18_110944.png > In Spark Thrift Server, CAST AS FLOAT inconsistent with spark-

[jira] [Updated] (SPARK-24829) CAST AS FLOAT inconsistent with Hive

2018-07-17 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-24829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-24829: Attachment: CAST-FLOAT.png > CAST AS FLOAT inconsistent with Hive > --

[jira] [Created] (SPARK-24829) CAST AS FLOAT inconsistent with Hive

2018-07-17 Thread zuotingbing (JIRA)
zuotingbing created SPARK-24829: --- Summary: CAST AS FLOAT inconsistent with Hive Key: SPARK-24829 URL: https://issues.apache.org/jira/browse/SPARK-24829 Project: Spark Issue Type: Bug

[jira] [Commented] (SPARK-19250) In security cluster, spark beeline connect to hive metastore failed

2018-05-29 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-19250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16493254#comment-16493254 ] zuotingbing commented on SPARK-19250: - Same problem in spark 2.2.1 . But We add kini

[jira] [Comment Edited] (SPARK-15544) Bouncing Zookeeper node causes Active spark master to exit

2018-04-17 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-15544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440535#comment-16440535 ] zuotingbing edited comment on SPARK-15544 at 4/17/18 8:02 AM: -

[jira] [Comment Edited] (SPARK-15544) Bouncing Zookeeper node causes Active spark master to exit

2018-04-17 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-15544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440535#comment-16440535 ] zuotingbing edited comment on SPARK-15544 at 4/17/18 8:01 AM: -

[jira] [Comment Edited] (SPARK-15544) Bouncing Zookeeper node causes Active spark master to exit

2018-04-17 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-15544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440535#comment-16440535 ] zuotingbing edited comment on SPARK-15544 at 4/17/18 7:53 AM: -

[jira] [Comment Edited] (SPARK-15544) Bouncing Zookeeper node causes Active spark master to exit

2018-04-17 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-15544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440535#comment-16440535 ] zuotingbing edited comment on SPARK-15544 at 4/17/18 7:51 AM: -

[jira] [Comment Edited] (SPARK-15544) Bouncing Zookeeper node causes Active spark master to exit

2018-04-17 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-15544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440535#comment-16440535 ] zuotingbing edited comment on SPARK-15544 at 4/17/18 7:49 AM: -

[jira] [Comment Edited] (SPARK-15544) Bouncing Zookeeper node causes Active spark master to exit

2018-04-17 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-15544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440535#comment-16440535 ] zuotingbing edited comment on SPARK-15544 at 4/17/18 7:49 AM: -

[jira] [Comment Edited] (SPARK-15544) Bouncing Zookeeper node causes Active spark master to exit

2018-04-17 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-15544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440535#comment-16440535 ] zuotingbing edited comment on SPARK-15544 at 4/17/18 7:48 AM: -

[jira] [Comment Edited] (SPARK-15544) Bouncing Zookeeper node causes Active spark master to exit

2018-04-17 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-15544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440535#comment-16440535 ] zuotingbing edited comment on SPARK-15544 at 4/17/18 7:48 AM: -

[jira] [Comment Edited] (SPARK-15544) Bouncing Zookeeper node causes Active spark master to exit

2018-04-17 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-15544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440535#comment-16440535 ] zuotingbing edited comment on SPARK-15544 at 4/17/18 7:47 AM: -

[jira] [Comment Edited] (SPARK-15544) Bouncing Zookeeper node causes Active spark master to exit

2018-04-17 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-15544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440535#comment-16440535 ] zuotingbing edited comment on SPARK-15544 at 4/17/18 7:45 AM: -

[jira] [Comment Edited] (SPARK-15544) Bouncing Zookeeper node causes Active spark master to exit

2018-04-17 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-15544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440535#comment-16440535 ] zuotingbing edited comment on SPARK-15544 at 4/17/18 7:44 AM: -

[jira] [Comment Edited] (SPARK-15544) Bouncing Zookeeper node causes Active spark master to exit

2018-04-17 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-15544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440535#comment-16440535 ] zuotingbing edited comment on SPARK-15544 at 4/17/18 7:43 AM: -

[jira] [Comment Edited] (SPARK-15544) Bouncing Zookeeper node causes Active spark master to exit

2018-04-17 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-15544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440535#comment-16440535 ] zuotingbing edited comment on SPARK-15544 at 4/17/18 7:43 AM: -

[jira] [Commented] (SPARK-15544) Bouncing Zookeeper node causes Active spark master to exit

2018-04-17 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-15544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440535#comment-16440535 ] zuotingbing commented on SPARK-15544: - cc [~vanzin] > Bouncing Zookeeper node causes

[jira] [Commented] (SPARK-15544) Bouncing Zookeeper node causes Active spark master to exit

2018-04-17 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-15544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440511#comment-16440511 ] zuotingbing commented on SPARK-15544: - The same issue still occurs in spark 2.3.0.  

[jira] [Updated] (SPARK-23745) Remove the directories of the “hive.downloaded.resources.dir” when HiveThriftServer2 stopped

2018-03-20 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-23745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-23745: Description: !2018-03-20_164832.png!   when start the HiveThriftServer2, we create some directorie

[jira] [Updated] (SPARK-23745) Remove the directories of the “hive.downloaded.resources.dir” when HiveThriftServer2 stopped

2018-03-20 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-23745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-23745: Description: !2018-03-20_164832.png!   when start the HiveThriftServer2, we create some  directori

[jira] [Updated] (SPARK-23745) Remove the directories of the “hive.downloaded.resources.dir” when HiveThriftServer2 stopped

2018-03-20 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-23745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-23745: Description:   when start the HiveThriftServer2, we create some  directories for hive.downloaded.

[jira] [Updated] (SPARK-23745) Remove the directories of the “hive.downloaded.resources.dir” when HiveThriftServer2 stopped

2018-03-20 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-23745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-23745: Attachment: 2018-03-20_164832.png > Remove the directories of the “hive.downloaded.resources.dir” w

[jira] [Created] (SPARK-23745) Remove the directories of the “hive.downloaded.resources.dir” when HiveThriftServer2 stopped

2018-03-20 Thread zuotingbing (JIRA)
zuotingbing created SPARK-23745: --- Summary: Remove the directories of the “hive.downloaded.resources.dir” when HiveThriftServer2 stopped Key: SPARK-23745 URL: https://issues.apache.org/jira/browse/SPARK-23745

[jira] [Updated] (SPARK-23547) Cleanup the .pipeout file when the Hive Session closed

2018-03-06 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-23547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-23547: Description:   !2018-03-07_121010.png!   when the hive session closed, we should also cleanup the

[jira] [Updated] (SPARK-23547) Cleanup the .pipeout file when the Hive Session closed

2018-03-06 Thread zuotingbing (JIRA)
[ https://issues.apache.org/jira/browse/SPARK-23547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zuotingbing updated SPARK-23547: Description:   !2018-03-07_121010.png! when the hive session closed, we should also cleanup the .p

  1   2   3   >