ignite-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dma...@apache.org
Subject svn commit: r1826052 - in /ignite/site/trunk/arch: durablememory.html persistence.html
Date Tue, 06 Mar 2018 23:43:03 GMT
Author: dmagda
Date: Tue Mar  6 23:43:03 2018
New Revision: 1826052

URL: http://svn.apache.org/viewvc?rev=1826052&view=rev
Log:
updated persistence

Modified:
    ignite/site/trunk/arch/durablememory.html
    ignite/site/trunk/arch/persistence.html

Modified: ignite/site/trunk/arch/durablememory.html
URL: http://svn.apache.org/viewvc/ignite/site/trunk/arch/durablememory.html?rev=1826052&r1=1826051&r2=1826052&view=diff
==============================================================================
--- ignite/site/trunk/arch/durablememory.html (original)
+++ ignite/site/trunk/arch/durablememory.html Tue Mar  6 23:43:03 2018
@@ -77,7 +77,16 @@ under the License.
                 indexes on disk (assuming that Ignite Native Persistence is enabled), while
Virtual Memory uses the
                 disk when it runs out of RAM, for swapping purposes only.
             </p>
-
+            <h2 style="padding-top: 10px;">Ignite Native Persistence</h2>
+            <p>
+                Ignite Persistence is the most flexible, scalable, and convenient way of
persisting data in Ignite.
+                It is widely used in scenarios where applications need a distributed memory-centric
database
+            </p>
+            <p>
+                Ignite native persistence is a distributed, ACID, and <nobr>SQL-compliant</nobr>
disk store
+                that transparently integrates with Ignite's durable memory. Ignite persistence
is optional
+                and can be turned on and off. When turned off Ignite becomes a pure in-memory
store.
+            </p>
             <p>
                 Following are the advantages and characteristics of Apache Ignite as a platform
when Durable Memory
                 and Ignite Native Persistence are used together:
@@ -105,7 +114,33 @@ under the License.
                     <li>Instantaneous Cluster Restarts</li>
                 </ul>
             </div>
-            <p>Read more on the <a href="https://apacheignite.readme.io/docs/durable-memory"
target="_blank">main documentation page</a>.</p>
+
+            <h2 style="padding-top: 10px;">3rd Party Persistence</h2>
+            <p>
+                Ignite can be used as a caching layer (aka. data grid) above an existing
3rd party
+                database - RDBMS, NoSQL, or HDFS. This mode is used to accelerate the underlying
database that persists
+                the data. Ignite stores data in memory, distributed across multiple nodes
providing fast data access.
+                It reduces the network overhead caused due to frequent data movement between
an application and the database.
+                However, there are some limitations in comparison to the native persistence.
For instance, SQL queries
+                will be executed only on the data that is in RAM, thus, requiring to preload
all the data set from disk
+                to memory beforehand.
+            </p>
+
+            <h2 style="padding-top: 10px;">Swap Space</h2>
+            <p>
+                If you do not want to use Ignite native persistence or 3rd party persistence,
you can enable swapping,
+                in which case, Ignite in-memory data will be moved to the swap space located
on disk if you run out of RAM.
+                When swap space is enabled, Ignites stores data in memory mapped files (MMF)
whose content will be
+                swapped to disk by the OS depending on the current RAM consumption. The swap
space is mostly used to
+                avoid out of memory errors (OOME) that might happen if RAM consumption goes
beyond its capacity and
+                you need more time to scale the cluster out to​ redistribute the data
sets evenly.
+            </p>
+
+            <div class="page-heading">More Information</div>
+            <p><a href="https://apacheignite.readme.io/docs/durable-memory" target="_blank">Durable
Memory</a>.</p>
+            <p><a href="https://apacheignite.readme.io/docs/distributed-persistent-store"
target="_blank">Native Persistence</a></p>
+            <p><a href="https://apacheignite.readme.io/docs/3rd-party-store" target="_blank">3rd
Party Persistence</a></p>
+            <p><a href="https://apacheignite.readme.io/docs/swap-space" target="_blank">Swap
Space</a></p>
         </section>
     </main>
 

Modified: ignite/site/trunk/arch/persistence.html
URL: http://svn.apache.org/viewvc/ignite/site/trunk/arch/persistence.html?rev=1826052&r1=1826051&r2=1826052&view=diff
==============================================================================
--- ignite/site/trunk/arch/persistence.html (original)
+++ ignite/site/trunk/arch/persistence.html Tue Mar  6 23:43:03 2018
@@ -54,148 +54,124 @@ under the License.
     <main id="main" role="main" class="container">
         <section id="native-persistence" class="page-section">
             <h1 class="first">Ignite Persistence</h1>
-                <div class="col-sm-12 col-md-12 col-xs-12" style="padding-left:0; padding-right:0;">
-                    <div class="col-sm-6 col-md-6 col-xs-12" style="padding-left:0; padding-right:0;">
-                        <p>
-                            Ignite is widely used as a caching layer above an existing 3rd
-                            party database, such as RDBMS, Apache Cassandra or MongoDB, to
-                            accelerate them. At the same time, Ignite comes with its own
persistence that is considered as an alternate
-                            and preferable persistence layer for an Ignite cluster.
-                        </p>
-                        <h2 style="padding-top: 10px;">Native Persistence</h2>
-                        <p>
-                            Ignite native persistence is a distributed, ACID, and <nobr>SQL-compliant</nobr>
disk store
-                            that transparently integrates with Ignite's durable memory. Ignite
persistence is optional
-                            and can be turned on and off. When turned off Ignite becomes
a pure in-memory store.
-                        </p>
-
-                    </div>
-                    <div class="col-sm-6 col-md-6 col-xs-12" style="padding-right:0; top:
-10px;">
-                        <a href="/images/native_persistence.png"><img class="img-responsive"
src="/images/native_persistence.png" width="450px" style="float:right;" alt="Apache Ignite
Native Persistence - Distributed SQL Database"/></a>
-                    </div>
+            <div class="col-sm-12 col-md-12 col-xs-12" style="padding-left:0; padding-right:0;">
+                <div class="col-sm-6 col-md-6 col-xs-12" style="padding-left:0; padding-right:0;">
+                    <p>
+                        Ignite is widely used as a caching layer above an existing 3rd
+                        party database, such as RDBMS, Apache Cassandra or MongoDB, to
+                        accelerate them. At the same time, Ignite comes with its own persistence
that is considered as an alternate
+                        and preferable persistence layer for an Ignite cluster.
+                    </p>
+                    <p>
+                        Ignite native persistence is a distributed, ACID, and <nobr>SQL-compliant</nobr>
disk store
+                        that transparently integrates with Ignite's durable memory. Ignite
persistence is optional
+                        and can be turned on and off. When turned off Ignite becomes a pure
in-memory store.
+                    </p>
+
+                </div>
+                <div class="col-sm-6 col-md-6 col-xs-12" style="padding-right:0; top:
-10px;">
+                    <a href="/images/native_persistence.png"><img class="img-responsive"
src="/images/native_persistence.png" width="450px" style="float:right;" alt="Apache Ignite
Native Persistence - Distributed SQL Database"/></a>
                 </div>
-                <p>
-                    With the the native persistence enabled, Ignite always stores a superset
of data on disk,
-                    and as much as possible in RAM. For example, if there are
-                    100 entries and RAM has the capacity to store only 20, then all 100 will
be stored on disk
-                    and only 20 will be cached in RAM for better performance.
-                </p>
-                <p>
-                    The native persistence has the following important characteristics:
-                </p>
+            </div>
+            <p>
+                With the the native persistence enabled, Ignite always stores a superset
of data on disk,
+                and as much as possible in RAM. For example, if there are
+                100 entries and RAM has the capacity to store only 20, then all 100 will
be stored on disk
+                and only 20 will be cached in RAM for better performance.
+            </p>
+            <p>
+                The native persistence has the following important characteristics:
+            </p>
+            <ul class="page-list" style="margin-bottom: 20px;">
+                <li>
+                    SQL queries over the full data set that spans both, memory and disk.
This means that Apache
+                    Ignite can be used as a memory-centric distributed SQL database.
+                </li>
+                <li>
+                    No need to have all the data in memory. Ignite persistence allows storing
a superset
+                    of data on disk and only most frequently used subsets in memory.
+                </li>
+                <li>
+                    Instantaneous cluster restarts. Ignite becomes fully operational from
disk immediately
+                    upon cluster startup or restart. There is no need to preload or warm
up the in-memory caches.
+                    The data will be loaded in-memory lazily, as it gets accessed.
+                </li>
+                <li>
+                    Data and indexes are stored in a similar format both in memory and on
disk, which helps avoid
+                    expensive transformations when moving data between memory and disk.
+                </li>
+                <li>
+                    Ability to create full and incremental cluster snapshots by plugging-in
3rd party solutions.
+                </li>
+            </ul>
+
+            <div class="page-heading">Write-Ahead Log</div>
+            <p>
+                Every time the data is updated in memory, the update will be appended to
the tail of
+                the write-ahead log (WAL). The purpose of the WAL is to propagate updates
to disk in
+                the fastest way possible and provide a consistent recovery mechanism that
supports full cluster failures.
+            </p>
+            <p>
+                The whole WAL is split into several files, called segments, that are filled
out sequentially.
+                Once a segment is full, its content will be copied to the <i>WAL archive</i>
where it will be preserved
+                for a configurable amount of time. While the segment is being copied, another
segment
+                will be treated as an active WAL file.
+            </p>
+            <p>
+                The cluster can always be recovered up to the latest successfully committed
transaction.
+            </p>
+
+            <div class="page-heading">Checkpointing</div>
+            <p>
+                As WAL grows, it periodically gets <i>checkpointed</i> to the
main storage.
+                The checkpointing is the process of copying <i>dirty pages</i>
from memory to the partition files on disk.
+                A dirty page is a page that was updated in memory, was appended to WAL, but
was not written to a respective partition
+                file on disk yet.
+            </p>
+            <div class="page-heading">Durability</div>
+            <p>
+                Ignite native persistence provides ACID durability guarantees to the data:
+
                 <ul class="page-list" style="margin-bottom: 20px;">
+                    <li>Committed transactions will always survive any failures.</li>
                     <li>
-                        SQL queries over the full data set that spans both, memory and disk.
This means that Apache
-                        Ignite can be used as a memory-centric distributed SQL database.
-                    </li>
-                    <li>
-                        No need to have all the data in memory. Ignite persistence allows
storing a superset
-                        of data on disk and only most frequently used subsets in memory.
-                    </li>
-                    <li>
-                        Instantaneous cluster restarts. Ignite becomes fully operational
from disk immediately
-                        upon cluster startup or restart. There is no need to preload or warm
up the in-memory caches.
-                        The data will be loaded in-memory lazily, as it gets accessed.
-                    </li>
-                    <li>
-                        Data and indexes are stored in a similar format both in memory and
on disk, which helps avoid
-                        expensive transformations when moving data between memory and disk.
+                        The cluster can always be recovered to the latest successfully committed
transaction.
                     </li>
                     <li>
-                        Ability to create full and incremental cluster snapshots by plugging-in
3rd party solutions.
+                        The cluster restarts are very fast.
                     </li>
                 </ul>
+            </p>
+            <div class="page-heading">Configuration</div>
+            <p>
+                To enable Ignite persistence, add the following configuration parameter to
the cluster's
+                node configuration:
+            </p>
+            <div class="tab-content">
+                <div class="tab-pane active" id="configuration">
+                    <pre class="brush:xml">
+                        <bean class="org.apache.ignite.configuration.IgniteConfiguration">
+                            <!-- Enabling Apache Ignite native persistence. -->
+                            <property name="dataStorageConfiguration">
+                                <bean class="org.apache.ignite.configuration.DataStorageConfiguration">
+                                    <property name="defaultDataRegionConfiguration">
+                                        <bean class="org.apache.ignite.configuration.DataRegionConfiguration">
+                                            <property name="persistenceEnabled" value="true"/>
+                                        </bean>
+                                    </property>
+                                </bean>
+                            </property>
 
-                <div class="page-heading">Write-Ahead Log</div>
-                <p>
-                    Every time the data is updated in memory, the update will be appended
to the tail of
-                    the write-ahead log (WAL). The purpose of the WAL is to propagate updates
to disk in
-                    the fastest way possible and provide a consistent recovery mechanism
that supports full cluster failures.
-                </p>
-                <p>
-                    The whole WAL is split into several files, called segments, that are
filled out sequentially.
-                    Once a segment is full, its content will be copied to the <i>WAL
archive</i> where it will be preserved
-                    for a configurable amount of time. While the segment is being copied,
another segment
-                    will be treated as an active WAL file.
-                </p>
-                <p>
-                    The cluster can always be recovered up to the latest successfully committed
transaction.
-                </p>
-
-                <div class="page-heading">Checkpointing</div>
-                <p>
-                    As WAL grows, it periodically gets <i>checkpointed</i> to
the main storage.
-                    The checkpointing is the process of copying <i>dirty pages</i>
from memory to the partition files on disk.
-                    A dirty page is a page that was updated in memory, was appended to WAL,
but was not written to a respective partition
-                    file on disk yet.
-                </p>
-                <div class="page-heading">Durability</div>
-                <p>
-                    Ignite native persistence provides ACID durability guarantees to the
data:
-
-                    <ul class="page-list" style="margin-bottom: 20px;">
-                        <li>Committed transactions will always survive any failures.</li>
-                        <li>
-                            The cluster can always be recovered to the latest successfully
committed transaction.
-                        </li>
-                        <li>
-                            The cluster restarts are very fast.
-                        </li>
-                    </ul>
-                </p>
-                <div class="page-heading">Configuration</div>
-                <p>
-                    To enable Ignite persistence, add the following configuration parameter
to the cluster's
-                    node configuration:
-                </p>
-                <div class="tab-content">
-                    <div class="tab-pane active" id="configuration">
-                        <pre class="brush:xml">
-                            <bean class="org.apache.ignite.configuration.IgniteConfiguration">
-                                <!-- Enabling Apache Ignite native persistence. -->
-                                <property name="dataStorageConfiguration">
-                                    <bean class="org.apache.ignite.configuration.DataStorageConfiguration">
-                                        <property name="defaultDataRegionConfiguration">
-                                            <bean class="org.apache.ignite.configuration.DataRegionConfiguration">
-                                                <property name="persistenceEnabled" value="true"/>
-                                            </bean>
-                                        </property>
-                                    </bean>
-                                </property>
-
-                                <!-- Additional setting. -->
+                            <!-- Additional setting. -->
 
-                                </bean>
-                        </pre>
-                    </div>
+                            </bean>
+                    </pre>
                 </div>
+            </div>
 
-            <h2 style="padding-top: 10px;">3rd Party Persistence</h2>
-            <p>
-                Ignite can be used as a caching layer (aka. data grid) above an existing
3rd party
-                database - RDBMS, NoSQL, or HDFS. This mode is used to accelerate the underlying
database that persists
-                the data. Ignite stores data in memory, distributed across multiple nodes
providing fast data access.
-                It reduces the network overhead caused due to frequent data movement between
an application and the database.
-                However, there are some limitations in comparison to the native persistence.
For instance, SQL queries
-                will be executed only on the data that is in RAM, thus, requiring to preload
all the data set from disk
-                to memory beforehand.
-            </p>
-
-            <h2 style="padding-top: 10px;">Swap Space</h2>
-            <p>
-                If you do not want to use Ignite native persistence or 3rd party persistence,
you can enable swapping,
-                in which case, Ignite in-memory data will be moved to the swap space located
on disk if you run out of RAM.
-                When swap space is enabled, Ignites stores data in memory mapped files (MMF)
whose content will be
-                swapped to disk by the OS depending on the current RAM consumption. The swap
space is mostly used to
-                avoid out of memory errors (OOME) that might happen if RAM consumption goes
beyond its capacity and
-                you need more time to scale the cluster out to​ redistribute the data
sets evenly.
-            </p>
-
-            <div class="page-heading">More Information</div>
-            <p><a href="https://apacheignite.readme.io/docs/distributed-persistent-store"
target="_blank">Native Persistence</a></p>
-            <p><a href="https://apacheignite.readme.io/docs/3rd-party-store" target="_blank">3rd
Party Persistence</a></p>
-            <p><a href="https://apacheignite.readme.io/docs/swap-space" target="_blank">Swap
Space</a></p>
+            <p><a href="https://apacheignite.readme.io/docs/distributed-persistent-store"
target="_blank">Read more</a></p>
         </section>
+
     </main>
 
     <!--#include virtual="/includes/footer.html" -->



Mime
View raw message