Hi, Roman
Sorry about that I missed one question just now.
> if the two configuration options are still in use, why does the FLIP
propose to deprecate them?
These two configs are usually used to avoid the memory issue, but
after introducing the improvement, generally, I think it is no longer
Hi, devs,
I'd like to start a discuss about adding an option called
"table.oprimizer.busy-join-reorder-threshold" for planner rule while we try
to introduce a new busy join reorder rule[1] into Flink.
This join reorder rule is based on dynamic programing[2], which can store
all possible
Thanks for your question, Roman
> wouldn't it be more clear to separate motivation from the
proposed changes?
All the contents in the motivation part are the current implementation
of Shuffle reading.
The Flip has described where ExclusiveBuffersPerChannel
and FloatingBuffersPerGate is from, the
Yunfeng Zhou created FLINK-30532:
Summary: Add benchmark for DCT, SQLTransformer and
StopWordsRemover algorithm
Key: FLINK-30532
URL: https://issues.apache.org/jira/browse/FLINK-30532
Project: Flink
Dong Lin created FLINK-30531:
Summary: Reduce operator chain call stack depth
Key: FLINK-30531
URL: https://issues.apache.org/jira/browse/FLINK-30531
Project: Flink
Issue Type: Improvement
Arseniy Tashoyan created FLINK-30530:
Summary: Flink configuration from user-provided ConfigMap
Key: FLINK-30530
URL: https://issues.apache.org/jira/browse/FLINK-30530
Project: Flink
Gyula Fora created FLINK-30529:
--
Summary: Use simple cancel for savepoint upgrades on failing jobs
Key: FLINK-30529
URL: https://issues.apache.org/jira/browse/FLINK-30529
Project: Flink
Issue
Gyula Fora created FLINK-30528:
--
Summary: Job may be stuck in upgrade loop when last-state fallback
is disabled and deployment is missing
Key: FLINK-30528
URL: https://issues.apache.org/jira/browse/FLINK-30528
Gyula Fora created FLINK-30527:
--
Summary: Last-state suspend followed by flinkVersion change may
lead to state loss
Key: FLINK-30527
URL: https://issues.apache.org/jira/browse/FLINK-30527
Project: Flink
Martijn Visser created FLINK-30526:
--
Summary: Handle failures in OpenSearch with
ActionRequestFailureHandler being deprecated
Key: FLINK-30526
URL: https://issues.apache.org/jira/browse/FLINK-30526
Weihua Hu created FLINK-30525:
-
Summary: Cannot open jobmanager configuration web page
Key: FLINK-30525
URL: https://issues.apache.org/jira/browse/FLINK-30525
Project: Flink
Issue Type: Bug
Thanks for your reply Yuxin,
> ExclusiveBuffersPerChannel and FloatingBuffersPerGate are obtained from
> configurations, which are not calculated. I have described them in the
FLIP
> motivation section.
The motivation section says about floating buffers:
> FloatingBuffersPerGate is within the
Hi, JasonLee
Thanks for the feedback.
> How can we determine how many RS and IG a DAG has?
Network memory is related to the parallelism and the complexity of the task
DAG, which I think is correct. However, this Flip can only improve the part
issue of the total issue, mainly focusing on memory
Yongming Zhang created FLINK-30524:
--
Summary: Unify the style of the logs page
Key: FLINK-30524
URL: https://issues.apache.org/jira/browse/FLINK-30524
Project: Flink
Issue Type: Improvement
weibo zhao created FLINK-30523:
--
Summary: Refine benchmark of vectorAssembler
Key: FLINK-30523
URL: https://issues.apache.org/jira/browse/FLINK-30523
Project: Flink
Issue Type: Improvement
Hi Yuxin
Thanks for the proposal, big + 1 for this FLIP.
It is difficult for users to calculate the size of network memory. If the
setting is too small, the task cannot be started. If the setting is too large,
there may be a waste of resources. As far as possible, Flink framework can
yuzelin created FLINK-30522:
---
Summary: `SHOW TBLPROPERTIES` can't read properties of table in
Spark3
Key: FLINK-30522
URL: https://issues.apache.org/jira/browse/FLINK-30522
Project: Flink
Issue
Hi, Roman
Thanks for the replay.
ExclusiveBuffersPerChannel and FloatingBuffersPerGate are obtained from
configurations, which are not calculated. I have described them in the FLIP
motivation section.
> 3. Each gate requires at least one buffer...
The timeout exception occurs when the
yuzelin created FLINK-30521:
---
Summary: Improve `Altering Tables` of Doc
Key: FLINK-30521
URL: https://issues.apache.org/jira/browse/FLINK-30521
Project: Flink
Issue Type: Improvement
Thanks for all your feedback!
To @Yuxia,
> What the sink expect to do to isolate data produced by speculative
> executions? IIUC, if the taks failover, it also generate a new attempt.
> Does it make difference in isolating data produced?
Yes there is something different from the task failover
tanjialiang created FLINK-30520:
---
Summary: Arguments contains with '#' will error split in
loadYAMLResource
Key: FLINK-30520
URL: https://issues.apache.org/jira/browse/FLINK-30520
Project: Flink
Gyula Fora created FLINK-30519:
--
Summary: Add e2e tests for operator dynamic config
Key: FLINK-30519
URL: https://issues.apache.org/jira/browse/FLINK-30519
Project: Flink
Issue Type: New
Binh-Nguyen Tran created FLINK-30518:
Summary: [flink-operator] Kubernetes HA not working due to wrong
jobmanager.rpc.address
Key: FLINK-30518
URL: https://issues.apache.org/jira/browse/FLINK-30518
Weihua Hu created FLINK-30517:
-
Summary: Decrease log output interval while waiting for YARN
JobManager be allocated
Key: FLINK-30517
URL: https://issues.apache.org/jira/browse/FLINK-30517
Project: Flink
24 matches
Mail list logo
