I have a multi-tenant system where each tenant has their own index. It
is sometimes required to restore a tenant to its previous state.
Is it possible to backup and restore each index (tenant) separately?
More specifically:
Can I backup each index data folder in the gateway separately?
Can I restore each index data folder to the gateway separately?
What about the metadata? It holds data for all the indexes so when
I restore a index folder it may be our of sync with the metadata.
How do I empty the transaction log of data related to an index
before I restore it? Do I need to flush? I wouldn't want to have data
in the index that is both from the restored index and from the
transaction log that was flushed after the restore.
Can I somehow shutdown an index, and tell it to reload from the
gateway (and ignore its work folder)?
No, there isn't support for per index management to this degree. Can be
implemented, with various difficulties depending on what exactly is needed.
For example, just snapshotting an index to a gateway, and then restoring
from it is simple. The metadata is the more complex part since it is not
stored on a per index leve, but globally.
I have a multi-tenant system where each tenant has their own index. It
is sometimes required to restore a tenant to its previous state.
Is it possible to backup and restore each index (tenant) separately?
More specifically:
Can I backup each index data folder in the gateway separately?
Can I restore each index data folder to the gateway separately?
What about the metadata? It holds data for all the indexes so when
I restore a index folder it may be our of sync with the metadata.
How do I empty the transaction log of data related to an index
before I restore it? Do I need to flush? I wouldn't want to have data
in the index that is both from the restored index and from the
transaction log that was flushed after the restore.
Can I somehow shutdown an index, and tell it to reload from the
gateway (and ignore its work folder)?
Is this something you are planning for a future release?
I think that it is an important use case for multi-tenant
applications. In many cases you even let the customer (tenant owner or
admin) initiate the restore on their own.
No, there isn't support for per index management to this degree. Can be
implemented, with various difficulties depending on what exactly is needed.
For example, just snapshotting an index to a gateway, and then restoring
from it is simple. The metadata is the more complex part since it is not
stored on a per index leve, but globally.
I have a multi-tenant system where each tenant has their own index. It
is sometimes required to restore a tenant to its previous state.
Is it possible to backup and restore each index (tenant) separately?
More specifically:
Can I backup each index data folder in the gateway separately?
Can I restore each index data folder to the gateway separately?
What about the metadata? It holds data for all the indexes so when
I restore a index folder it may be our of sync with the metadata.
How do I empty the transaction log of data related to an index
before I restore it? Do I need to flush? I wouldn't want to have data
in the index that is both from the restored index and from the
transaction log that was flushed after the restore.
Can I somehow shutdown an index, and tell it to reload from the
gateway (and ignore its work folder)?
Agreed, it is important. Can you open an issue for this? I am currently
working on 0.9.1 and want to close what I plan, will try and schedule it for
the next version.
Is this something you are planning for a future release?
I think that it is an important use case for multi-tenant
applications. In many cases you even let the customer (tenant owner or
admin) initiate the restore on their own.
No, there isn't support for per index management to this degree. Can be
implemented, with various difficulties depending on what exactly is
needed.
For example, just snapshotting an index to a gateway, and then restoring
from it is simple. The metadata is the more complex part since it is not
stored on a per index leve, but globally.
I have a multi-tenant system where each tenant has their own index. It
is sometimes required to restore a tenant to its previous state.
Is it possible to backup and restore each index (tenant) separately?
More specifically:
Can I backup each index data folder in the gateway separately?
Can I restore each index data folder to the gateway separately?
What about the metadata? It holds data for all the indexes so when
I restore a index folder it may be our of sync with the metadata.
How do I empty the transaction log of data related to an index
before I restore it? Do I need to flush? I wouldn't want to have data
in the index that is both from the restored index and from the
transaction log that was flushed after the restore.
Can I somehow shutdown an index, and tell it to reload from the
gateway (and ignore its work folder)?
Agreed, it is important. Can you open an issue for this? I am currently
working on 0.9.1 and want to close what I plan, will try and schedule it for
the next version.
Is this something you are planning for a future release?
I think that it is an important use case for multi-tenant
applications. In many cases you even let the customer (tenant owner or
admin) initiate the restore on their own.
No, there isn't support for per index management to this degree. Can be
implemented, with various difficulties depending on what exactly is
needed.
For example, just snapshotting an index to a gateway, and then restoring
from it is simple. The metadata is the more complex part since it is not
stored on a per index leve, but globally.
I have a multi-tenant system where each tenant has their own index. It
is sometimes required to restore a tenant to its previous state.
Is it possible to backup and restore each index (tenant) separately?
More specifically:
Can I backup each index data folder in the gateway separately?
Can I restore each index data folder to the gateway separately?
What about the metadata? It holds data for all the indexes so when
I restore a index folder it may be our of sync with the metadata.
How do I empty the transaction log of data related to an index
before I restore it? Do I need to flush? I wouldn't want to have data
in the index that is both from the restored index and from the
transaction log that was flushed after the restore.
Can I somehow shutdown an index, and tell it to reload from the
gateway (and ignore its work folder)?
Agreed, it is important. Can you open an issue for this? I am currently
working on 0.9.1 and want to close what I plan, will try and schedule it for
the next version.
Is this something you are planning for a future release?
I think that it is an important use case for multi-tenant
applications. In many cases you even let the customer (tenant owner or
admin) initiate the restore on their own.
No, there isn't support for per index management to this degree. Can be
implemented, with various difficulties depending on what exactly is
needed.
For example, just snapshotting an index to a gateway, and then restoring
from it is simple. The metadata is the more complex part since it is not
stored on a per index leve, but globally.
I have a multi-tenant system where each tenant has their own index. It
is sometimes required to restore a tenant to its previous state.
Is it possible to backup and restore each index (tenant) separately?
More specifically:
Can I backup each index data folder in the gateway separately?
Can I restore each index data folder to the gateway separately?
What about the metadata? It holds data for all the indexes so when
I restore a index folder it may be our of sync with the metadata.
How do I empty the transaction log of data related to an index
before I restore it? Do I need to flush? I wouldn't want to have data
in the index that is both from the restored index and from the
transaction log that was flushed after the restore.
Can I somehow shutdown an index, and tell it to reload from the
gateway (and ignore its work folder)?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.