[jira] [Updated] (HDDS-25) Simple async event processing for SCM
[ https://issues.apache.org/jira/browse/HDDS-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anu Engineer updated HDDS-25: - Resolution: Fixed Status: Resolved (was: Patch Available) [~msingh] ,[~shashikant] Thanks for review comments. [~elek] Thanks for contribtuion. The patch v5 is beautiful and a pleasure to read. Thanks for getting this done. Really appreciate it. > Simple async event processing for SCM > - > > Key: HDDS-25 > URL: https://issues.apache.org/jira/browse/HDDS-25 > Project: Hadoop Distributed Data Store > Issue Type: Improvement > Components: SCM >Reporter: Elek, Marton >Assignee: Elek, Marton >Priority: Major > Fix For: 0.2.1 > > Attachments: HDDS-25.001.patch, HDDS-25.003.patch, HDDS-25.004.patch, > HDDS-25.005.patch > > > For implementing all the SCM status changes we need a simple async event > processing. > Our use-case is very similar to an actor based system: we would like to > communicate with full asny event/messages, process the different events on > different threads, ... > But a full Actor framework (such as Akka) would be overkill for this use > case. We don't need distributed actor systems, actor hierarchy or complex > resiliency. > As a first approach we can use a very simple system where a common EventQueue > entry point could route events to the async event handlers -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-25) Simple async event processing for SCM
[ https://issues.apache.org/jira/browse/HDDS-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elek, Marton updated HDDS-25: - Attachment: HDDS-25.005.patch > Simple async event processing for SCM > - > > Key: HDDS-25 > URL: https://issues.apache.org/jira/browse/HDDS-25 > Project: Hadoop Distributed Data Store > Issue Type: Improvement > Components: SCM >Reporter: Elek, Marton >Assignee: Elek, Marton >Priority: Major > Fix For: 0.2.1 > > Attachments: HDDS-25.001.patch, HDDS-25.003.patch, HDDS-25.004.patch, > HDDS-25.005.patch > > > For implementing all the SCM status changes we need a simple async event > processing. > Our use-case is very similar to an actor based system: we would like to > communicate with full asny event/messages, process the different events on > different threads, ... > But a full Actor framework (such as Akka) would be overkill for this use > case. We don't need distributed actor systems, actor hierarchy or complex > resiliency. > As a first approach we can use a very simple system where a common EventQueue > entry point could route events to the async event handlers -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-25) Simple async event processing for SCM
[ https://issues.apache.org/jira/browse/HDDS-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elek, Marton updated HDDS-25: - Attachment: HDDS-25.004.patch > Simple async event processing for SCM > - > > Key: HDDS-25 > URL: https://issues.apache.org/jira/browse/HDDS-25 > Project: Hadoop Distributed Data Store > Issue Type: Improvement > Components: SCM >Reporter: Elek, Marton >Assignee: Elek, Marton >Priority: Major > Fix For: 0.2.1 > > Attachments: HDDS-25.001.patch, HDDS-25.003.patch, HDDS-25.004.patch > > > For implementing all the SCM status changes we need a simple async event > processing. > Our use-case is very similar to an actor based system: we would like to > communicate with full asny event/messages, process the different events on > different threads, ... > But a full Actor framework (such as Akka) would be overkill for this use > case. We don't need distributed actor systems, actor hierarchy or complex > resiliency. > As a first approach we can use a very simple system where a common EventQueue > entry point could route events to the async event handlers -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-25) Simple async event processing for SCM
[ https://issues.apache.org/jira/browse/HDDS-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elek, Marton updated HDDS-25: - Attachment: (was: HDDS-25-HDDS-25.002.patch) > Simple async event processing for SCM > - > > Key: HDDS-25 > URL: https://issues.apache.org/jira/browse/HDDS-25 > Project: Hadoop Distributed Data Store > Issue Type: Improvement > Components: SCM >Reporter: Elek, Marton >Assignee: Elek, Marton >Priority: Major > Fix For: 0.2.1 > > Attachments: HDDS-25.001.patch, HDDS-25.003.patch > > > For implementing all the SCM status changes we need a simple async event > processing. > Our use-case is very similar to an actor based system: we would like to > communicate with full asny event/messages, process the different events on > different threads, ... > But a full Actor framework (such as Akka) would be overkill for this use > case. We don't need distributed actor systems, actor hierarchy or complex > resiliency. > As a first approach we can use a very simple system where a common EventQueue > entry point could route events to the async event handlers -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-25) Simple async event processing for SCM
[ https://issues.apache.org/jira/browse/HDDS-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elek, Marton updated HDDS-25: - Attachment: HDDS-25.003.patch > Simple async event processing for SCM > - > > Key: HDDS-25 > URL: https://issues.apache.org/jira/browse/HDDS-25 > Project: Hadoop Distributed Data Store > Issue Type: Improvement > Components: SCM >Reporter: Elek, Marton >Assignee: Elek, Marton >Priority: Major > Fix For: 0.2.1 > > Attachments: HDDS-25.001.patch, HDDS-25.003.patch > > > For implementing all the SCM status changes we need a simple async event > processing. > Our use-case is very similar to an actor based system: we would like to > communicate with full asny event/messages, process the different events on > different threads, ... > But a full Actor framework (such as Akka) would be overkill for this use > case. We don't need distributed actor systems, actor hierarchy or complex > resiliency. > As a first approach we can use a very simple system where a common EventQueue > entry point could route events to the async event handlers -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-25) Simple async event processing for SCM
[ https://issues.apache.org/jira/browse/HDDS-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elek, Marton updated HDDS-25: - Attachment: HDDS-25-HDDS-25.002.patch > Simple async event processing for SCM > - > > Key: HDDS-25 > URL: https://issues.apache.org/jira/browse/HDDS-25 > Project: Hadoop Distributed Data Store > Issue Type: Improvement > Components: SCM >Reporter: Elek, Marton >Assignee: Elek, Marton >Priority: Major > Fix For: 0.2.1 > > Attachments: HDDS-25-HDDS-25.002.patch, HDDS-25.001.patch > > > For implementing all the SCM status changes we need a simple async event > processing. > Our use-case is very similar to an actor based system: we would like to > communicate with full asny event/messages, process the different events on > different threads, ... > But a full Actor framework (such as Akka) would be overkill for this use > case. We don't need distributed actor systems, actor hierarchy or complex > resiliency. > As a first approach we can use a very simple system where a common EventQueue > entry point could route events to the async event handlers -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-25) Simple async event processing for SCM
[ https://issues.apache.org/jira/browse/HDDS-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elek, Marton updated HDDS-25: - Status: Patch Available (was: Open) First version. Please let me know what do you think about this approach (cc [~nandakumar131], [~msingh], [~anu]). I removed the annotation based implementation as it can't guarantee compile time type safety (could be guaranteed with annotation processor but IDE won't detect it. With simple generic types we can see the errors even before the compilation, thanks to the IDE). > Simple async event processing for SCM > - > > Key: HDDS-25 > URL: https://issues.apache.org/jira/browse/HDDS-25 > Project: Hadoop Distributed Data Store > Issue Type: Improvement > Components: SCM >Reporter: Elek, Marton >Assignee: Elek, Marton >Priority: Major > Fix For: 0.2.1 > > Attachments: HDDS-25.001.patch > > > For implementing all the SCM status changes we need a simple async event > processing. > Our use-case is very similar to an actor based system: we would like to > communicate with full asny event/messages, process the different events on > different threads, ... > But a full Actor framework (such as Akka) would be overkill for this use > case. We don't need distributed actor systems, actor hierarchy or complex > resiliency. > As a first approach we can use a very simple system where a common EventQueue > entry point could route events to the async event handlers -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-25) Simple async event processing for SCM
[ https://issues.apache.org/jira/browse/HDDS-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elek, Marton updated HDDS-25: - Attachment: HDDS-25.001.patch > Simple async event processing for SCM > - > > Key: HDDS-25 > URL: https://issues.apache.org/jira/browse/HDDS-25 > Project: Hadoop Distributed Data Store > Issue Type: Improvement > Components: SCM >Reporter: Elek, Marton >Assignee: Elek, Marton >Priority: Major > Fix For: 0.2.1 > > Attachments: HDDS-25.001.patch > > > For implementing all the SCM status changes we need a simple async event > processing. > Our use-case is very similar to an actor based system: we would like to > communicate with full asny event/messages, process the different events on > different threads, ... > But a full Actor framework (such as Akka) would be overkill for this use > case. We don't need distributed actor systems, actor hierarchy or complex > resiliency. > As a first approach we can use a very simple system where a common EventQueue > entry point could route events to the async event handlers -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
