Uploaded image for project: 'Red Hat Data Grid'
  1. Red Hat Data Grid
  2. JDG-495

Administraion Guide review Chapters I. - V.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • JDG 7.0.0 CR1
    • JDG 7.0.0 ER9
    • Documentation
    • None

      If you find any of the fix suggestion too brief, don't hesitate to ask me

      • [ 3.1. About Expiration | http://docbuilder.usersys.redhat.com/23161/#About_Expiration ]
        Attribute "maxIdle" is changed to "max-idle" and is the same in library and client-server mode. Attributes "reaperEnabled" and "wakeUpInterval" don't exist anymore, hence the configuration is again the same for library and client-server mode.
      • [ 4.2. Supported Application Logging Frameworks | http://docbuilder.usersys.redhat.com/23161/#sect-Supported_Application_Logging_Frameworks ]
        "JBoss Logging, which is included with Red Hat JBoss Data Grid 6." - adjust JDG version
        "JBoss Logging is the application logging framework that is included in JBoss Enterprise Application Platform 6. As a result of this inclusion, Red Hat JBoss Data Grid 6 also uses JBoss Logging. " - adjust JDG and EAP versions
      • [ Configure Local Mode (Remote Client-Server Mode) | http://docbuilder.usersys.redhat.com/23161/#Configure_Local_Mode ]
        The code snippet contains example of configuration of the local cache. I think it should be as simple as possible and there is extra configuration "indexing" element, which basically has nothing to do with it. I would remove it and add comment like "<!-- Additional configuration information here -->" which is present in many other code snippets.
      • [ 5.4. State Transfer | http://docbuilder.usersys.redhat.com/23161/#sect-State_Transfer ]
        I think this section should be moved after the section about distributed and replicated caches. E.g. this chapter talks about "numOwners", but it wasn't mentioned before anywhere. This is just my suggestion, feel free to ignore it (but after consideration! ).
      • [ 6.5. Configure Distribution Mode (Remote Client-Server Mode) | http://docbuilder.usersys.redhat.com/23161/#Configure_Distribution_Mode ]
        The "executor" attribute of "transport" element is only applicable in the library mode, you cannot use it in the client-server mode. But it's not related really to the distributed cache, it's more JGroups option and there is a note below "JGroups must be appropriately configured for clustered mode before attempting to load this configuration.", so I think it's OK to omit the "transport" element in the code snippet.
        Also there is last sentence in the section "For details about the cache-container, locking, and transaction elements, see the appropriate chapter." In the code snippet, there is no locking or transaction element, hence it doesn't really make sense. Plus it doesn't have any link to "appropriate chapters", so I think it could be simply removed.
      • [ 7.3. Configure Replication Mode (Remote Client-Server Mode) | http://docbuilder.usersys.redhat.com/23161/#Configure_Replication_Mode1 ]
        Same thing as with the "indexing" element as I mentioned above. There is "transaction" element, which is not directly relevant to replicated cache configuration, hence I would suggest removing it to make it as simple as possible and add a comment "<!-- Additional configuration information here -->".
      • [ 9.1. Batching API | http://docbuilder.usersys.redhat.com/23161/#Batching_API ]
        Sentence "Batching may be enabled on a per-cache basis by defining a transaction mode of BATCHING. The following example demonstrates this:" contains mode "BATCHING". It's actually just "BATCH", just like the code snippet says.
      • 10.3.3. Infinispan Directory Provider
        In the code snippter there is line: 
        <property name="default.directory_provider">filesystem</property

        It contains wrong value and misses last ">", hence change it to:

        <property name="default.directory_provider">infinispan</property
      • [ 11.1.1. Configure REST Connectors | http://docbuilder.usersys.redhat.com/23161/#Configure_REST_Connectors1 ]
        The code snippet and the text are really similiar with the 11.1 introduction, maybe we can merge them together? Also the code snippet needs correction, change the namespace from "urn:infinispan:server:endpoint:6.1" to "urn:infinispan:server:endpoint:8.0" and remove the "virtual-server" attribute, which no longer exists.
      • [ 13.4.1. Configure Hot Rod Connectors | http://docbuilder.usersys.redhat.com/23161/#Configure_Hot_Rod_Connectors1 ]
        The code snippet should be (changed namespace, corrected "hotrod-connector" enclosing "topology-state-transfer" and removed "await-initial-transfer"): 
        <subsystem xmlns="urn:infinispan:server:endpoint:6.1">
	<hotrod-connector socket-binding="hotrod" 
			  cache-container="local" 
			  worker-threads="${VALUE}" 
			  idle-timeout="${VALUE}"
			  tcp-nodelay="${TRUE/FALSE}"
			  send-buffer-size="${VALUE}"
			  receive-buffer-size="${VALUE}" >
		<topology-state-transfer lock-timeout"="${MILLISECONDS}"
				 replication-timeout="${MILLISECONDS}"
				 external-host="${HOSTNAME}"
				 external-port="${PORT}"
				 lazy-retrieval="${TRUE/FALSE}"  /> 
	</hotrod-connector>
</subsystem>

      Since the "await-initial-transfer" no longer exists, remove it also from the description.

      Well, I guess that all for now

            jholusa Jiří Holuša (Inactive)
            jholusa Jiří Holuša (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: