[jira] [Commented] (BEAM-10053) Timers exception on "Job Drain" while using stateful beam processing in global window

[ https://issues.apache.org/jira/browse/BEAM-10053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17165981#comment-17165981 ] MOHIL commented on BEAM-10053: -- Issue still exists and need triaging > Timers exception on

[jira] [Updated] (BEAM-10053) Timers exception on "Job Drain" while using stateful beam processing in global window

[ https://issues.apache.org/jira/browse/BEAM-10053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MOHIL updated BEAM-10053: - Labels: P2 (was: stale-P2) > Timers exception on "Job Drain" while using stateful beam processing in > global w

[jira] [Updated] (BEAM-10339) Getting PC: @ 0x7f7490e08602 (unknown) raise and Check failure stack trace: ***

[ https://issues.apache.org/jira/browse/BEAM-10339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MOHIL updated BEAM-10339: - Description: I am using the BEAM java 2.19.0 version on google dataflow.   Default machine type which is n1-sta

[jira] [Updated] (BEAM-10339) Getting PC: @ 0x7f7490e08602 (unknown) raise and Check failure stack trace: ***

[ https://issues.apache.org/jira/browse/BEAM-10339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MOHIL updated BEAM-10339: - Attachment: dataflow_step_job_id_2020-06-25_01_11_47-8571841088706513966__logs__2020-06-25T01-15.json > Getting

[jira] [Updated] (BEAM-10339) Getting PC: @ 0x7f7490e08602 (unknown) raise and Check failure stack trace: ***

[ https://issues.apache.org/jira/browse/BEAM-10339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MOHIL updated BEAM-10339: - Attachment: working-workerlogs.png screenshot2.png screenshot1.png

[jira] [Created] (BEAM-10339) Getting PC: @ 0x7f7490e08602 (unknown) raise and Check failure stack trace: ***

MOHIL created BEAM-10339: Summary: Getting PC: @ 0x7f7490e08602 (unknown) raise and Check failure stack trace: *** Key: BEAM-10339 URL: https://issues.apache.org/jira/browse/BEAM-10339 Project: Beam

[jira] [Commented] (BEAM-10053) Timers exception on "Job Drain" while using stateful beam processing in global window

[ https://issues.apache.org/jira/browse/BEAM-10053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17118160#comment-17118160 ] MOHIL commented on BEAM-10053: -- Can we set allowedLateness on globalWindow ? What does it me

[jira] [Created] (BEAM-10053) Timers exception on "Job Drain" while using stateful beam processing in global window

MOHIL created BEAM-10053: Summary: Timers exception on "Job Drain" while using stateful beam processing in global window Key: BEAM-10053 URL: https://issues.apache.org/jira/browse/BEAM-10053 Project: Beam

[jira] [Created] (BEAM-10019) Keeping keys in a state for a very long time (keys expiry unknown)

MOHIL created BEAM-10019: Summary: Keeping keys in a state for a very long time (keys expiry unknown) Key: BEAM-10019 URL: https://issues.apache.org/jira/browse/BEAM-10019 Project: Beam Issue Type: