[infinispan-issues] [JBoss JIRA] (ISPN-4584) Stricter validation of cache configurations for distributed indexes

[Gustavo Fernandes (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-4584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989415#comment-12989415 ] 

Gustavo Fernandes edited comment on ISPN-4584 at 7/31/14 5:43 AM:
------------------------------------------------------------------

 I was thinking in a typesafe config to serve to both power users and beginners. It would make validation easier at the same time controlling what is exposed or not (I think there are currently +30 possible properties that can be used)

Minimally for disk indexes:
{code:xml}
<indexing>
   <storage>
      <filesystem/>
   </storage>
</indexing>
{code}

Minimally for infinispan indexes:
{code:xml}
<indexing>
   <storage>
      <infinispan/>
    </storage>
</indexing>
{code}

Dr. Manhattan version:
{code:xml}
<indexing>
   <storage>
      <infinispan>
          <metadata-storage>
               <distributed-cache name="superFancyMetadataStorage" mode="SYNC" segments="20" owners="2" remote-timeout="30000" start="EAGER">
                   <locking acquire-timeout="30000" concurrency-level="1000" striping="false" />
                   <transaction mode="NONE" />
               </distributed-cache>
          </metadataStorage>
          <data-storage>
              <replicated-cache name="jackpotTimeout" mode="SYNC" remote-timeout="17501">
                  <state-transfer timeout="60000" enabled="true"/>
              </replicated-cache>
          </data-storage>
          <lock-storage>
            ... 
           </lock-storage>
     </infinispan>
   </storage>
   <reader strategy="shared"/>
   <writer>
        <merge min-size="1000" max-size="10000" max-queue-length="10000"/>
        <worker type="ASYNC">
            <thread-pool size="10"/>
            <queue max="1000"/>
        </worker>
   </writer>
</indexing>   
{code}

and for compatibility, allowing it mutually exclusive with the above configs
{code:xml}
<indexing>
  <properties>...</properties>
</indexing>
{code}

finally for "don't bother me, index it already!" users:

{code:xml}
<indexing auto-config="true">
</indexing>
{code}




was (Author: gustavonalle):
 I was thinking in a typesafe config to serve to both power users and beginners. It would make validation easier at the same time controlling what is exposed or not (I think there are currently +30 possible properties that can be used)

Minimally for disk indexes:
{code:xml}
<indexing>
   <storage>
      <filesystem/>
   </storage>
</indexing>
{code}

Minimally for infinispan indexes:
{code:xml}
<indexing>
   <storage>
      <infinispan/>
    </storage>
</indexing>
{code}

Dr. Manhattan version:
{code:xml}
<indexing>
   <storage>
      <infinispan>
          <metadata-storage>
               <distributed-cache name="superFancyMetadataStorage" mode="SYNC" segments="20" owners="2" remote-timeout="30000" start="EAGER">
                   <locking acquire-timeout="30000" concurrency-level="1000" striping="false" />
                   <transaction mode="NONE" />
               </distributed-cache>
          </metadataStorage>
          <data-storage>
              <replicated-cache name="jackpotTimeout" mode="SYNC" remote-timeout="17501">
                  <state-transfer timeout="60000" enabled="true"/>
              </replicated-cache>
          </data-storage>
          <lock-storage>
            ... 
           </lock-storage>
     </infinispan>
   </storage>
   <reader strategy="shared"/>
   <writer>
        <merge min-size="1000" max-size="10000" max-queue-length="10000"/>
        <worker type="ASYNC">
            <thread-pool size="10">
            <queue max="1000"/>
            </thread-pool>
        </worker>
   </writer>
</indexing>   
{code}

and for compatibility, allowing it mutually exclusive with the above configs
{code:xml}
<indexing>
  <properties>...</properties>
</indexing>
{code}

finally for "don't bother me, index it already!" users:

{code:xml}
<indexing auto-config="true">
</indexing>
{code}



> Stricter validation of cache configurations for distributed indexes
> -------------------------------------------------------------------
>
>                 Key: ISPN-4584
>                 URL: https://issues.jboss.org/browse/ISPN-4584
>             Project: Infinispan
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Lucene Directory
>            Reporter: Sanne Grinovero
>            Assignee: Gustavo Fernandes
>            Priority: Minor
>
> See also ISPN-4577 : it should not be allowed to configure a distributed metadata cache while the chunks cache is using local mode.
> Ideally think of additional strict checks which we should apply.. suggestions?
> Mitigated by ISPN-4340



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)