[tickets] [opensaf:tickets] #3019 imm: return try-again on write requests when FS is unresponsive
- Description has changed: Diff: --- old +++ new @@ -1,4 +1,4 @@ -With current design, when the file system (FS) is neither available nor responsive, CCB apply on IMM OM side likely get SA_AIS_ERR_TIMEOUT error code as osafpbed may be stuck at the activity of writing to sqlite3 database and therefore is not able to response to IMM in time. +With current design, when the file system (FS) is neither available nor responsive, CCB apply on IMM OM side likely get SA_AIS_ERR_TIMEOUT error code as osafpbed may be stuck at the activity of writing to sqlite3 database and therefore is not able to respond to IMM in time. With this ticket, we propose to introduce 02 new admin operations (set/clear) towards IMM; using these operations to inform IMM if the file system is unavailable or in healthy state. Based on that data, IMM will reject the write request earlier with error code SA_AIS_ERR_TRY_AGAIN if the file system is unavailable. --- ** [tickets:#3019] imm: return try-again on write requests when FS is unresponsive** **Status:** assigned **Milestone:** 5.19.03 **Created:** Mon Mar 18, 2019 03:57 AM UTC by Vu Minh Nguyen **Last Updated:** Mon Mar 18, 2019 04:59 AM UTC **Owner:** Vu Minh Nguyen With current design, when the file system (FS) is neither available nor responsive, CCB apply on IMM OM side likely get SA_AIS_ERR_TIMEOUT error code as osafpbed may be stuck at the activity of writing to sqlite3 database and therefore is not able to respond to IMM in time. With this ticket, we propose to introduce 02 new admin operations (set/clear) towards IMM; using these operations to inform IMM if the file system is unavailable or in healthy state. Based on that data, IMM will reject the write request earlier with error code SA_AIS_ERR_TRY_AGAIN if the file system is unavailable. Besides, a runtime attribute `saImmFileSystemStatus` is added and owned by IMM to show the status of underlying file system. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #3019 imm: return try-again on write requests when FS is unresponsive
- Description has changed: Diff: --- old +++ new @@ -1,4 +1,4 @@ -With current design, when the file system (FS) is either unavailable or responsive, CCB apply on IMM OM side likely get SA_AIS_ERR_TIMEOUT error code as osafpbed may be stuck at the activity of writing to sqlite3 database and therefore is not able to response to IMM in time. +With current design, when the file system (FS) is neither available nor responsive, CCB apply on IMM OM side likely get SA_AIS_ERR_TIMEOUT error code as osafpbed may be stuck at the activity of writing to sqlite3 database and therefore is not able to response to IMM in time. With this ticket, we propose to introduce 02 new admin operations (set/clear) towards IMM; using these operations to inform IMM if the file system is unavailable or in healthy state. Based on that data, IMM will reject the write request earlier with error code SA_AIS_ERR_TRY_AGAIN if the file system is unavailable. --- ** [tickets:#3019] imm: return try-again on write requests when FS is unresponsive** **Status:** assigned **Milestone:** 5.19.03 **Created:** Mon Mar 18, 2019 03:57 AM UTC by Vu Minh Nguyen **Last Updated:** Mon Mar 18, 2019 04:51 AM UTC **Owner:** Vu Minh Nguyen With current design, when the file system (FS) is neither available nor responsive, CCB apply on IMM OM side likely get SA_AIS_ERR_TIMEOUT error code as osafpbed may be stuck at the activity of writing to sqlite3 database and therefore is not able to response to IMM in time. With this ticket, we propose to introduce 02 new admin operations (set/clear) towards IMM; using these operations to inform IMM if the file system is unavailable or in healthy state. Based on that data, IMM will reject the write request earlier with error code SA_AIS_ERR_TRY_AGAIN if the file system is unavailable. Besides, a runtime attribute `saImmFileSystemStatus` is added and owned by IMM to show the status of underlying file system. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #3019 imm: return try-again on write requests when FS is unresponsive
- **summary**: imm: return try-again on write requests when file system is unresponsive --> imm: return try-again on write requests when FS is unresponsive - Description has changed: Diff: --- old +++ new @@ -1,4 +1,4 @@ -With current design, when the file system is unavailable or not responsive, CCB apply on IMM OM side likely get SA_AIS_ERR_TIMEOUT error code as osafpbed may stuck at the activity of writing to sqlite3 database and therefore is not able to response to IMM in time. +With current design, when the file system (FS) is either unavailable or responsive, CCB apply on IMM OM side likely get SA_AIS_ERR_TIMEOUT error code as osafpbed may be stuck at the activity of writing to sqlite3 database and therefore is not able to response to IMM in time. With this ticket, we propose to introduce 02 new admin operations (set/clear) towards IMM; using these operations to inform IMM if the file system is unavailable or in healthy state. Based on that data, IMM will reject the write request earlier with error code SA_AIS_ERR_TRY_AGAIN if the file system is unavailable. --- ** [tickets:#3019] imm: return try-again on write requests when FS is unresponsive** **Status:** assigned **Milestone:** 5.19.03 **Created:** Mon Mar 18, 2019 03:57 AM UTC by Vu Minh Nguyen **Last Updated:** Mon Mar 18, 2019 04:30 AM UTC **Owner:** Vu Minh Nguyen With current design, when the file system (FS) is either unavailable or responsive, CCB apply on IMM OM side likely get SA_AIS_ERR_TIMEOUT error code as osafpbed may be stuck at the activity of writing to sqlite3 database and therefore is not able to response to IMM in time. With this ticket, we propose to introduce 02 new admin operations (set/clear) towards IMM; using these operations to inform IMM if the file system is unavailable or in healthy state. Based on that data, IMM will reject the write request earlier with error code SA_AIS_ERR_TRY_AGAIN if the file system is unavailable. Besides, a runtime attribute `saImmFileSystemStatus` is added and owned by IMM to show the status of underlying file system. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #3019 imm: return try-again on write requests when file system is unresponsive
- **status**: unassigned --> assigned - **assigned_to**: Vu Minh Nguyen --- ** [tickets:#3019] imm: return try-again on write requests when file system is unresponsive** **Status:** assigned **Milestone:** 5.19.03 **Created:** Mon Mar 18, 2019 03:57 AM UTC by Vu Minh Nguyen **Last Updated:** Mon Mar 18, 2019 03:58 AM UTC **Owner:** Vu Minh Nguyen With current design, when the file system is unavailable or not responsive, CCB apply on IMM OM side likely get SA_AIS_ERR_TIMEOUT error code as osafpbed may stuck at the activity of writing to sqlite3 database and therefore is not able to response to IMM in time. With this ticket, we propose to introduce 02 new admin operations (set/clear) towards IMM; using these operations to inform IMM if the file system is unavailable or in healthy state. Based on that data, IMM will reject the write request earlier with error code SA_AIS_ERR_TRY_AGAIN if the file system is unavailable. Besides, a runtime attribute `saImmFileSystemStatus` is added and owned by IMM to show the status of underlying file system. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #3019 imm: return try-again on write requests when file system is unresponsive
- Description has changed: Diff: --- old +++ new @@ -2,4 +2,4 @@ With this ticket, we propose to introduce 02 new admin operations (set/clear) towards IMM; using these operations to inform IMM if the file system is unavailable or in healthy state. Based on that data, IMM will reject the write request earlier with error code SA_AIS_ERR_TRY_AGAIN if the file system is unavailable. -Besides, an runtime attribute `saImmFileSystemStatus` is added and owned by IMM to show the status of underlying file system. +Besides, a runtime attribute `saImmFileSystemStatus` is added and owned by IMM to show the status of underlying file system. --- ** [tickets:#3019] imm: return try-again on write requests when file system is unresponsive** **Status:** unassigned **Milestone:** 5.19.03 **Created:** Mon Mar 18, 2019 03:57 AM UTC by Vu Minh Nguyen **Last Updated:** Mon Mar 18, 2019 03:57 AM UTC **Owner:** nobody With current design, when the file system is unavailable or not responsive, CCB apply on IMM OM side likely get SA_AIS_ERR_TIMEOUT error code as osafpbed may stuck at the activity of writing to sqlite3 database and therefore is not able to response to IMM in time. With this ticket, we propose to introduce 02 new admin operations (set/clear) towards IMM; using these operations to inform IMM if the file system is unavailable or in healthy state. Based on that data, IMM will reject the write request earlier with error code SA_AIS_ERR_TRY_AGAIN if the file system is unavailable. Besides, a runtime attribute `saImmFileSystemStatus` is added and owned by IMM to show the status of underlying file system. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #3019 imm: return try-again on write requests when file system is unresponsive
--- ** [tickets:#3019] imm: return try-again on write requests when file system is unresponsive** **Status:** unassigned **Milestone:** 5.19.03 **Created:** Mon Mar 18, 2019 03:57 AM UTC by Vu Minh Nguyen **Last Updated:** Mon Mar 18, 2019 03:57 AM UTC **Owner:** nobody With current design, when the file system is unavailable or not responsive, CCB apply on IMM OM side likely get SA_AIS_ERR_TIMEOUT error code as osafpbed may stuck at the activity of writing to sqlite3 database and therefore is not able to response to IMM in time. With this ticket, we propose to introduce 02 new admin operations (set/clear) towards IMM; using these operations to inform IMM if the file system is unavailable or in healthy state. Based on that data, IMM will reject the write request earlier with error code SA_AIS_ERR_TRY_AGAIN if the file system is unavailable. Besides, an runtime attribute `saImmFileSystemStatus` is added and owned by IMM to show the status of underlying file system. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets