[
https://issues.apache.org/jira/browse/TRAFODION-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15691945#comment-15691945
]
Selvaganesan Govindarajan commented on TRAFODION-2306:
------------------------------------------------------
This PR #777 change was attributed to DamagedWalException (DEW) seen in region
server (RS) logs in Esgyn internal testing. This is primarily a client side
change except that co-processors are always added as the table attribute when a
trafodion table is created. Prior to this change, the coprocessors are added
when the attribute hbase.coprocessor.region.classes is not visible on the
client side. This is the case with CDH distro. However, the service side
configuration should continue to see the attribute
hbase.coprocessor.region.classes set to regionObserver, endpoint coprocessor
and AggregateCoprocesor classes both in CDH and HDP distros. It is possible
that RS can be influenced in some way due to double loading of these classes.
But, it was confirmed by @narendragoyal that the DWE is seen even when the
coprocessor is not added as the table attribute.
I read the change again to check if something is amiss with this change. I
couldn't find anything. Reviewers/Contributors, can you please review this
change again to determine what can possibly DWE due to the change.
> Trafodion customization using its own configuration file.
> ---------------------------------------------------------
>
> Key: TRAFODION-2306
> URL: https://issues.apache.org/jira/browse/TRAFODION-2306
> Project: Apache Trafodion
> Issue Type: Improvement
> Components: dtm, sql-general
> Reporter: Selvaganesan Govindarajan
> Assignee: Selvaganesan Govindarajan
>
> From: Selva Govindarajan [mailto:[email protected]]
> Sent: Friday, October 21, 2016 6:15 PM
> To: [email protected]
> Subject: [DISCUSS] Introducing Trafodion customization using its own
> configuration file.
>
> Currently Trafodion uses the standard client side Hbase configuration
> file hbase-site.xml deployed by the distros. It is found that there are
> variations in this configuration file between distros. At times, the distro
> manager decides that a given property is not a client property and it is not
> added to the deployed hbase client configuration file. In addition, there are
> certain properties like hbase.coprocessor.region.classes need to be
> configured for Trafodion tables for the transaction management. Hence, I am
> planning to introduce a configuration file traf-site.xml specific to
> Trafodion similar to hbase configuration file hbase-site.xml. This
> configuration file extends the properties inherited from the standard
> hbase-site.xml.
>
> By default, the traf-site.xml comes with the following properties
>
> <?xml version="1.0"?>
> <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
>
> <!-- Put Trafodion site-specific property overrides in this file. -->
>
> <configuration>
> <property>
> <name>hbase.hregion.impl</name>
>
> <value>org.apache.hadoop.hbase.regionserver.transactional.TransactionalRegion</value>
> </property>
> <property>
> <name>hbase.coprocessor.region.classes</name>
> <value>
>
> org.apache.hadoop.hbase.coprocessor.transactional.TrxRegionObserver,
>
> org.apache.hadoop.hbase.coprocessor.transactional.TrxRegionEndpoint,
> org.apache.hadoop.hbase.coprocessor.AggregateImplementation
> </value>
> </property>
> <property>
> <name>hbase.client.scanner.timeout.period</name>
> <value>3600000</value>
> </property>
> </configuration>
>
> This property file will be installed if it doesn't exist at
> $MY_SQROOT/etc directory when sqgen is done. Any client side property can be
> added to this file and the client connections from Trafodion client processes
> will inherit them.
>
> The hbase.coprocessor.region.classes are added as Table co-processor to
> the table descriptor when a Trafodion table is created. Trafodion installer
> will not be adding to these properties to hbase configuration file soon.
>
> Please feel free to provide your valuable suggestions/comments.
>
> Thanks
> Selva
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
