Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

maximum retry number not matching with exchange.max-retry-count value #307

Open
ahanapradhan opened this issue Mar 7, 2022 · 0 comments
Open

maximum retry number not matching with exchange.max-retry-count value #307

ahanapradhan opened this issue Mar 7, 2022 · 0 comments

Comments

@ahanapradhan
Copy link
Contributor

Software Environment:

  • OpenLooKeng version (source or binary):

  • OS platform & distribution (eg., Linux Ubuntu 16.04):

  • Java version:

Describe the current behavior

exchange.max-retry-count=20 (configured value)

query fails after retrying 21, 23, 24 times.. this number is most of the time not equal to 20.

When exchange.max-retry-count is not explicitly specified, it should retry for 10 times (default value)
But query fails after retrying for 15 times.

Different executions give different numbers.

Describe the expected behavior

query retry should happen exactly the number of time it is set in exchange.max-retry-count config parameter.

Steps to reproduce the issue

Related log/screenshots

Special notes for this issue
ahanapradhan added a commit to ahanapradhan/hetu-core that referenced this issue Mar 7, 2022
@ahanapradhan
issue openlookeng#307
98e38f2 
actual retry number not matching exchange.max-retry-count.
ahanapradhan added a commit to ahanapradhan/hetu-core that referenced this issue Mar 7, 2022
@ahanapradhan
issue openlookeng#307
3c08153 
actual retry number not matching exchange.max-retry-count.

restore logic of getRandomString for external function register

Signed-off-by: chenpingzeng <chenpingzeng@huawei.com>

[I4UMZH] Kryo Serialization Integration For Snapshot

Adding Secondary Spilling For OrderByOperator.

doc changes for RELOAD CUBE and SHOW CREATE CUBE

updated the ui document to show execution timeout property with its default value

handle exclusion of incomplete spill files for snapshots

Document update for enabling asynchronous spill mechanism for order by.

Changes to record snapshot capture metrics

updated ui execution timeout to 100 days, also updated document

SpilledJoinOptimizations, spiller blooms for eliminating spill probe
Added support for right outer scan when Build side spills.

Updating snapshot documentation with statastics details

Adding Configuration To Support Spilling In HDFS.

Corrected spelling mistakes in snapshot doc

Add varchar predicate limitation in cube documentation

Removing nodeId for creating HDFS spill subdirectories.
@ahanapradhan ahanapradhan mentioned this issue Mar 7, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant
@ahanapradhan