xcluster | Algorithms and evaluation tools for extreme clustering | Machine Learning library
kandi X-RAY | xcluster Summary
kandi X-RAY | xcluster Summary
xcluster contains algorithms and evaluation tools for extreme clustering, i.e., instances of clustering in which the number of points to be clustered and the number of clusters is large. Most notably, xcluster contains an implementation of PERCH (Purity Enhancing Rotations for Cluster Hierachies). PERCH is an online extreme clustering algorithm that incrementally builds a tree with data points at its leaves. During the data point insertion procedure, PERCH performs rotations to keep the tree accurate and as balanced as possible. Empirical experiments show that PERCH produces purer trees faster than other algorithms; theoretical analysis shows that for separable data, PERCH builds trees with perfect dendrogram purity regardless of the order of the data. Technical details and analysis of the algorithm can be found in our paper: A Hierarchical Algorithm for Extreme Clustering.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of xcluster
xcluster Key Features
xcluster Examples and Code Snippets
Community Discussions
Trending Discussions on xcluster
QUESTION
Case 1:
When I deploy an application with Jenkins in an environment say E1, it works successfully. App gets deployed and no errors on Jenkins console output.
Case 2:
When I deploy the same application with Jenkins in another environment say E2, the deploy operation fails but the app does get deploy in the server. Though I get errors in Jenkins console. I am confused, Is it code issue or server issue, how can I fix it?
Below is the error in this case:
...Target state: deploy failed on Cluster xCluster
15:53:27 java.lang.NoSuchMethodError: org.springframework.util.ClassUtils.forName(Ljava/lang/String;)Ljava/lang/Class; 15:53:27 at org.springframework.oxm.jaxb.JaxbUtils.(JaxbUtils.java:44) 15:53:27 at org.springframework.oxm.jaxb.Jaxb2Marshaller.createJaxbContext(Jaxb2Marshaller.java:272) 15:53:27 at org.springframework.oxm.jaxb.AbstractJaxbMarshaller.afterPropertiesSet(AbstractJaxbMarshaller.java:125) 15:53:27 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1687) 15:53:27 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1624) 15:53:27 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:555) 15:53:27 at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483) 15:53:27 at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306) 15:53:27 at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230) 15:53:27 at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302) 15:53:27 at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197) 15:53:27 at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:761) 15:53:27 at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:867) 15:53:27 at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:543) 15:53:27 at org.springframework.boot.context.embedded.EmbeddedWebApplicationContext.refresh(EmbeddedWebApplicationContext.java:122) 15:53:27 at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:693) 15:53:27 at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:360) 15:53:27 at org.springframework.boot.SpringApplication.run(SpringApplication.java:303) 15:53:27 at org.springframework.boot.web.support.SpringBootServletInitializer.run(SpringBootServletInitializer.java:154) 15:53:27 at org.springframework.boot.web.support.SpringBootServletInitializer.createRootApplicationContext(SpringBootServletInitializer.java:134) 15:53:27 at org.springframework.boot.web.support.SpringBootServletInitializer.onStartup(SpringBootServletInitializer.java:87) 15:53:27 at org.springframework.web.SpringServletContainerInitializer.onStartup(SpringServletContainerInitializer.java:169) 15:53:27 at weblogic.servlet.internal.WebAppServletContext.initContainerInitializer(WebAppServletContext.java:1389) 15:53:27 at weblogic.servlet.internal.WebAppServletContext.initContainerInitializers(WebAppServletContext.java:1326) 15:53:27 at weblogic.servlet.internal.WebAppServletContext.initContainerInitializers(WebAppServletContext.java:1312) 15:53:27 at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1829) 15:53:27 at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2891) 15:53:27 at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1661) 15:53:27 at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:823) 15:53:27 at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleModuleWrapper.java:360) 15:53:27 at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleModuleWrapper.java:356) 15:53:27 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42) 15:53:27 at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:138) 15:53:27 at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124) 15:53:27 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:216) 15:53:27 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:211) 15:53:27 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42) 15:53:27 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:73) 15:53:27 at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:24) 15:53:27 at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:729) 15:53:27 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42) 15:53:27 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:258) 15:53:27 at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:61) 15:53:27 at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:165) 15:53:27 at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80) 15:53:27 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:587) 15:53:27 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150) 15:53:27 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116) 15:53:27 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:339) 15:53:27 at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:846) 15:53:27 at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1275) 15:53:27 at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:442) 15:53:27 at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:176) 15:53:27 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195) 15:53:27 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13) 15:53:27 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68) 15:53:27 at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:553) 15:53:27 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311) 15:53:27 at weblogic.work.ExecuteThread.run(ExecuteThread.java:263)
ANSWER
Answered 2018-Jul-19 at 20:58Appreciate the comments from Deinum and Roddy!
I was able to resolve the issue/error and the deploy operation was successful.
Here is what I did:
I found multiple versions of spring-oxm in my library. I had to remove the oldest one and and retained the latest one which came from spring-boot-starter-web-services kit. Once you have single version and latest version of spring-oxm jar, you should be able to build, test and deploy successfully.
This was the root cause of the issue.
QUESTION
I'm trying to create an Azure RM Template with SQL Server 2016 AlwaysOn Avaiability Group by using this base template http://4c74356b41.com/post5775 The template I linked is too complex for me. I just need to create 2 VMs and 1 Storage Account and apply proper DSC to the VMs. I'm getting the following error while applying configuration sql-primary and configuration sql-secondary to the both VMs:
...ANSWER
Answered 2017-Nov-16 at 10:08Just to sum up a bunch of points here:
- domain and sql accounts should be different
- sql cluster ip address should be in one of the cluster networks
- you need to precreate the dns name record for the load balancer (due to how i'm doing everything in parallel i've decided to put that functionallity into the domain provisioning dsc configurations)
- to check deployment you can use always on dashboard
Cannot find path 'HKLM:\SOFTWARE\Microsoft\PowerShell\3\DSC' because it does not exist.
Seems to be a general error being thrown when something goes wrong (at least I could never find a pattern why it appeared), so usually its safe to disregard that error, it will be gone when you fix the real error (in my experiecen, at least).
SQL provisioning fails (sometimes) with weird errors (usually dns\timing related). I'm not sure how this would behave in an environment where domain is precreated in advance. it might be less fragile overall. In my latest commit (at the time of writing) I believe I've addressed some of the stability issues, and I'm quite sure with domain, storage for backups, keyvault precreated those issues shouldn't be present at all.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install xcluster
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page