[ 
https://issues.apache.org/jira/browse/HDDS-4573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shiyou xin updated HDDS-4573:
-----------------------------
    Docs Text: 
Logs as following : 
2020-12-09 13:56:02,949 [main] WARN org.apache.hadoop.ozone.recon.ReconUtils: 
ozone.recon.db.dir is not configured. We recommend adding this setting. Falling 
back to ozone.metadata.dirs instead.
2020-12-09 13:56:02,950 [main] INFO 
org.apache.hadoop.ozone.recon.spi.impl.ReconContainerDBProvider: Last known 
container-key DB : /data1/ozone/meta/recon-container-key.db_1607492308261
2020-12-09 13:56:03,062 [main] WARN 
org.apache.hadoop.hdds.utils.db.DBStoreBuilder: ozone.recon.db.dir is not 
configured. We recommend adding this setting. Falling back to 
ozone.metadata.dirs instead.
2020-12-09 13:56:03,114 [main] INFO 
org.apache.hadoop.ozone.recon.persistence.DerbyDataSourceProvider: JDBC Url for 
Recon : jdbc:derby:${ozone.recon.db.dir}/ozone_recon_derby.db
2020-12-09 13:56:04,135 [main] INFO org.hadoop.ozone.recon.codegen.SqlDbUtils: 
Created derby database at jdbc:derby:${ozone.recon.db.dir}/ozone_recon_derby.db.
2020-12-09 13:56:04,423 [main] INFO 
org.apache.hadoop.ozone.recon.persistence.DerbyDataSourceProvider: JDBC Url for 
Recon : jdbc:derby:${ozone.recon.db.dir}/ozone_recon_derby.db
2020-12-09 13:56:04,425 [main] INFO org.hadoop.ozone.recon.codegen.SqlDbUtils: 
Created derby database at jdbc:derby:${ozone.recon.db.dir}/ozone_recon_derby.db.


  was:
2020-12-09 13:56:02,949 [main] WARN org.apache.hadoop.ozone.recon.ReconUtils: 
ozone.recon.db.dir is not configured. We recommend adding this setting. Falling 
back to ozone.metadata.dirs instead.
2020-12-09 13:56:02,950 [main] INFO 
org.apache.hadoop.ozone.recon.spi.impl.ReconContainerDBProvider: Last known 
container-key DB : /data1/ozone/meta/recon-container-key.db_1607492308261
2020-12-09 13:56:03,062 [main] WARN 
org.apache.hadoop.hdds.utils.db.DBStoreBuilder: ozone.recon.db.dir is not 
configured. We recommend adding this setting. Falling back to 
ozone.metadata.dirs instead.
2020-12-09 13:56:03,114 [main] INFO 
org.apache.hadoop.ozone.recon.persistence.DerbyDataSourceProvider: JDBC Url for 
Recon : jdbc:derby:${ozone.recon.db.dir}/ozone_recon_derby.db
2020-12-09 13:56:04,135 [main] INFO org.hadoop.ozone.recon.codegen.SqlDbUtils: 
Created derby database at jdbc:derby:${ozone.recon.db.dir}/ozone_recon_derby.db.
2020-12-09 13:56:04,423 [main] INFO 
org.apache.hadoop.ozone.recon.persistence.DerbyDataSourceProvider: JDBC Url for 
Recon : jdbc:derby:${ozone.recon.db.dir}/ozone_recon_derby.db
2020-12-09 13:56:04,425 [main] INFO org.hadoop.ozone.recon.codegen.SqlDbUtils: 
Created derby database at jdbc:derby:${ozone.recon.db.dir}/ozone_recon_derby.db.



> inconsistent path when the item "ozone.recon.db.dir" is not configured
> ----------------------------------------------------------------------
>
>                 Key: HDDS-4573
>                 URL: https://issues.apache.org/jira/browse/HDDS-4573
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: Ozone Recon
>    Affects Versions: 1.0.0
>            Reporter: Shiyou xin
>            Priority: Minor
>
> There is an inconsistent path when the item "ozone.recon.db.dir" is not 
> configured : 
> 1 : falling back to ozone.metadata.dirs instead, just same as 
> ozone.scm.db.dir/ozone.om.db.dir
> 2 : the jdbcUrl variable in ReconSqlDbConfig class set default value 
> (jdbc:derby:${ozone.recon.db.dir}/ozone_recon_derby.db)
> The second points assume that "ozone.recon.db.dir" is must be configured, but 
> it was not.
> The result is that it will create a path named "${ozone.recon.db.dir}" in 
> current directory, when
> 1. "ozone.recon.db.dir" is not configured
> 2. ReconSqlDbConfig.setJdbcUrl is not called.
> That maybe a bug.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to