You can translate the question and the replies:

Error when changing the local repositories home path for GIT integration

We would like to make the repositories home dir shared across the vdp servers to make the VDP cluster highly available. When we change the Local repositories home path any path other than default we are getting below error when trying to refresh environments. Supplied different home path localtions for testing: * /opt/denodo-platform/work/vdp/repositories * /data/repository **Also what is your recommendation for using VCS local repositories where git repos require to be shared accross cluster of two of more VDP's behind a Loadbalancer. The idea is local commits are reflected immediately to users connected to different vdp servers?** Error crops on on VCS environment tab: Error accessing the server: error obtaining environments list: Error processing VCS request VDP.log 97201015 [DNI(13643)-XXX.XXX.XX.XX-285] ERROR 2022-12-13T14:30:08.466 com.denodo.vdb.interpreter.execution.ListEnvironmentsAction [] - Error obtaining environments list: Error processing VCS request com.denodo.vdb.interpreter.execution.vcs.exception.VCSFileSystemException: Error processing VCS request at com.denodo.vdb.interpreter.execution.vcs.FileSystem.consolidate(Unknown Source) ~[denodo-vdp-server.jar:8.0.3] at com.denodo.vdb.interpreter.execution.vcs.VCSUtil.storeRepoFileSystem(Unknown Source) ~[denodo-vdp-server.jar:8.0.3] at com.denodo.vdb.interpreter.execution.ListEnvironmentsAction.exec(Unknown Source) [denodo-vdp-server.jar:8.0.3] at com.denodo.vdb.interpreter.execution.Action.run(Unknown Source) [denodo-vdp-server.jar:8.0.3] at com.denodo.vdb.interpreter.execution.processor.VDBActionProcessor.f3(Unknown Source) [denodo-vdp-server.jar:8.0.3] at com.denodo.vdb.interpreter.execution.processor.VDBActionProcessor.a3(Unknown Source) [denodo-vdp-server.jar:8.0.3] at com.denodo.vdb.interpreter.execution.processor.VDBActionProcessor.d3(Unknown Source) [denodo-vdp-server.jar:8.0.3] at com.denodo.vdb.interpreter.execution.processor.VDBActionProcessor.a3(Unknown Source) [denodo-vdp-server.jar:8.0.3] at com.denodo.vdb.interpreter.execution.Action.start(Unknown Source) [denodo-vdp-server.jar:8.0.3] at com.denodo.vdb.interpreter.execution.ExecutionEngine.execute(Unknown Source) [denodo-vdp-server.jar:8.0.3] at com.denodo.vdb.interpreter.execution.ExecutionEngine.execute(Unknown Source) [denodo-vdp-server.jar:8.0.3] at com.denodo.vdb.vdbinterface.server.QueryExecutorImpl.executeStatement(Unknown Source) [denodo-vdp-server.jar:8.0.3] at com.denodo.vdb.vdbinterface.server.QueryExecutorImpl.executeStatement(Unknown Source) [denodo-vdp-server.jar:8.0.3] at jdk.internal.reflect.GeneratedMethodAccessor385.invoke(Unknown Source) ~[?:?] at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?] at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?] at com.denodo.internal.o.a.r.server.ObjectRef.invoke(ObjectRef.java:110) [denodo-asyncrmi.jar:8.0.3] at com.denodo.internal.o.a.r.netty.RMIServerHandler.dispatch(RMIServerHandler.java:183) [denodo-asyncrmi.jar:8.0.3] at com.denodo.internal.o.a.r.netty.RMIServerHandler.channelRead(RMIServerHandler.java:81) [denodo-asyncrmi.jar:8.0.3] at com.denodo.internal.i.n.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) [denodo-asyncrmi.jar:8.0.3] at com.denodo.internal.i.n.channel.AbstractChannelHandlerContext.access$600(AbstractChannelHandlerContext.java:61) [denodo-asyncrmi.jar:8.0.3]
VCS DENODO
user
13-12-2022 09:38:22 -0500
code

1 Answer

Hi, You should be able to change the local repository folder but it's hard to say exactly what's going on here. One thing you could try is to change the log level for the VCS integration by entering the command "CALL LOGCONTROLLER('com.denodo.vdb.interpreter.execution.vcs', 'DEBUG')" in the VQL Shell. The logs will then record not just Errors but other information about what's happening as you try to change the repository path. If changing the logging level to Debug doesn't bring up anything obvious, if you have a valid support user, I would submit a new case to the support site so they can do a deep dive. Remember to change the log level back to "Error" with that same command when you've solved the issue to prevent performance problems from excessive logging. For your more general question about on ensuring commits are deployed properly across different service, there's a great best practice guide to [Deployments and Continous Integration](https://community.denodo.com/kb/en/view/document/Denodo%20Deployments%20and%20Continuous%20Integration) that's a very good starting place. Hope this helps!
Denodo Team
16-12-2022 12:22:32 -0500
code
You must sign in to add an answer. If you do not have an account, you can register here