[jira] [Commented] (IGNITE-5558) Add ability to read WAL outside of an Ignite node
[ https://issues.apache.org/jira/browse/IGNITE-5558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16077870#comment-16077870 ] ASF GitHub Bot commented on IGNITE-5558: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2174 > Add ability to read WAL outside of an Ignite node > - > > Key: IGNITE-5558 > URL: https://issues.apache.org/jira/browse/IGNITE-5558 > Project: Ignite > Issue Type: Improvement > Components: persistence >Affects Versions: 2.1 >Reporter: Alexey Goncharuk >Assignee: Dmitriy Pavlov > Fix For: 2.1 > > > Currently, the WAL iterator can be obtained from the WAL manager when an > Ignite node is up and running. > However, it may be extremely useful to read WAL in an 'offline' mode, when a > node is not started up. This may be required for crash analysis or to export > committed data to some external systems. > In the future we can make this even a public interface, however as a starting > point, I would like to keep it in private package because moving to the > public package will require Iterator and records to be public too. > So, as a starting point, we need: > * An object that will allow us to get WALIterator instances (probably, > should be closeable) > * A method on this object which will create an iterator by a file name or > file names > Using this object should not require an active Ignite instance running. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5558) Add ability to read WAL outside of an Ignite node
[ https://issues.apache.org/jira/browse/IGNITE-5558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16063282#comment-16063282 ] Dmitriy Pavlov commented on IGNITE-5558: https://github.com/apache/ignite/pull/2196 > Add ability to read WAL outside of an Ignite node > - > > Key: IGNITE-5558 > URL: https://issues.apache.org/jira/browse/IGNITE-5558 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.1 >Reporter: Alexey Goncharuk >Assignee: Dmitriy Pavlov > Fix For: 2.1 > > > Currently, the WAL iterator can be obtained from the WAL manager when an > Ignite node is up and running. > However, it may be extremely useful to read WAL in an 'offline' mode, when a > node is not started up. This may be required for crash analysis or to export > committed data to some external systems. > In the future we can make this even a public interface, however as a starting > point, I would like to keep it in private package because moving to the > public package will require Iterator and records to be public too. > So, as a starting point, we need: > * An object that will allow us to get WALIterator instances (probably, > should be closeable) > * A method on this object which will create an iterator by a file name or > file names > Using this object should not require an active Ignite instance running. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5558) Add ability to read WAL outside of an Ignite node
[ https://issues.apache.org/jira/browse/IGNITE-5558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055682#comment-16055682 ] Dmitriy Pavlov commented on IGNITE-5558: [~agoncharuk], thank you for your reply. For first case we should prefer human readable format, but for second machine readable format is required. That is reason why I think these cases are too different. Or in this issue we need only iterator imlementation? If yes, objects that iterator returns will be still internal object such as CheckpointRecord, DataRecord without any changes (in scope of this issue)? > Add ability to read WAL outside of an Ignite node > - > > Key: IGNITE-5558 > URL: https://issues.apache.org/jira/browse/IGNITE-5558 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.1 >Reporter: Alexey Goncharuk > Fix For: 2.1 > > > Currently, the WAL iterator can be obtained from the WAL manager when an > Ignite node is up and running. > However, it may be extremely useful to read WAL in an 'offline' mode, when a > node is not started up. This may be required for crash analysis or to export > committed data to some external systems. > In the future we can make this even a public interface, however as a starting > point, I would like to keep it in private package because moving to the > public package will require Iterator and records to be public too. > So, as a starting point, we need: > * An object that will allow us to get WALIterator instances (probably, > should be closeable) > * A method on this object which will create an iterator by a file name or > file names > Using this object should not require an active Ignite instance running. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5558) Add ability to read WAL outside of an Ignite node
[ https://issues.apache.org/jira/browse/IGNITE-5558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055643#comment-16055643 ] Alexey Goncharuk commented on IGNITE-5558: -- The end user is both an Ignite engineer (crash recovery analysis) and third-party users that want to export data to other systems. That's why I think it makes sense to make this interface public once we polish the use-cases and functionality. > Add ability to read WAL outside of an Ignite node > - > > Key: IGNITE-5558 > URL: https://issues.apache.org/jira/browse/IGNITE-5558 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.1 >Reporter: Alexey Goncharuk > Fix For: 2.1 > > > Currently, the WAL iterator can be obtained from the WAL manager when an > Ignite node is up and running. > However, it may be extremely useful to read WAL in an 'offline' mode, when a > node is not started up. This may be required for crash analysis or to export > committed data to some external systems. > In the future we can make this even a public interface, however as a starting > point, I would like to keep it in private package because moving to the > public package will require Iterator and records to be public too. > So, as a starting point, we need: > * An object that will allow us to get WALIterator instances (probably, > should be closeable) > * A method on this object which will create an iterator by a file name or > file names > Using this object should not require an active Ignite instance running. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5558) Add ability to read WAL outside of an Ignite node
[ https://issues.apache.org/jira/browse/IGNITE-5558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055639#comment-16055639 ] Dmitriy Pavlov commented on IGNITE-5558: Who is end user of this utility (class)? is it Ignite engineer? > Add ability to read WAL outside of an Ignite node > - > > Key: IGNITE-5558 > URL: https://issues.apache.org/jira/browse/IGNITE-5558 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.1 >Reporter: Alexey Goncharuk > Fix For: 2.1 > > > Currently, the WAL iterator can be obtained from the WAL manager when an > Ignite node is up and running. > However, it may be extremely useful to read WAL in an 'offline' mode, when a > node is not started up. This may be required for crash analysis or to export > committed data to some external systems. > In the future we can make this even a public interface, however as a starting > point, I would like to keep it in private package because moving to the > public package will require Iterator and records to be public too. > So, as a starting point, we need: > * An object that will allow us to get WALIterator instances (probably, > should be closeable) > * A method on this object which will create an iterator by a file name or > file names > Using this object should not require an active Ignite instance running. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
