How can I change default "MariaDB" default ports? Specifically:
4568 For Incremental State Transfer.
4444 For all other State Snapshot Transfer
Thanks,
This is controlled by wsrep_sst_receive_address and the "ist.recv_addr" option in wsrep_provider_options, as explained at the following page: https://ospi.fi/blog/mariadb-galera-firewall-configuration.html
If you are using Docker, see if this helps: http://withblue.ink/2016/03/09/galera-cluster-mariadb-coreos-and-docker-part-1.html
Related
Is it possible to configure a read-only server that remains slave even though no more masters are available with MariaDB Maxscale 6.
I tried it with a readconroute router, but that one turned the slave eventually in to a master as well.
/Theo
If you are using the mariadbmon monitor, you can use the servers_no_promotion parameter to list the server you want to remain read-only.
For galeramon there should be no need to keep servers as read-only as all functioning nodes are capable of receiving writes.
I have been tried couple of configuration files but not able to change?
Have you tried changing "Run/Debug configurations" in Guidewire Studio?
In Policy Center v8.0.4 there is a VM parameter "-Dgw.port=" to specify port number.
I found my self finally.
Go to PolicyCenter\.idea\runConfigurations\server.xml and change the port as you want as shown below.
Ok so this might be a basic question, but i'm new to kubernetes and tried to install wordpress using helm unto it, using the stable/wordpress chart, but i keep getting an error "pod has unbound immediate PersistentVolumeClaims (repeated 2 times)" is this because of the requirement in here https://github.com/helm/charts/tree/master/stable/wordpress. "PV provisioner support in the underlying infrastructure" how do i enable this in my infrastructure, i have setup my cluster across three nodes on digitalocean, i've tried searching for tutorials on this, with no luck until now. Please let me know what i'm missing, thanks.
PersistentVolume types are implemented as plugins. Kubernetes currently supports the following plugins:
GCEPersistentDisk
AWSElasticBlockStore
AzureFile
AzureDisk
FC (Fibre Channel)
Flexvolume
Flocker
NFS
iSCSI
RBD (Ceph Block Device)
CephFS
Cinder (OpenStack block storage)
Glusterfs
VsphereVolume
Quobyte Volumes
HostPath (Single node testing only – local storage is not supported in any way and WILL NOT WORK in a multi-node cluster)
Portworx Volumes
ScaleIO Volumes
StorageOS
You can enable support for PVs or Dynamic PVs using thoese plugins.
detail reference
On Digital Ocean you can use block storage for volumes.
details
Kubernetes can be set-up for Dynamic Volume Provisioning. This would allow the Chart to run to completion using the default configuration as the PVs would be provisioned on-demand.
My setup is as the following:
MaxScale 2.1.4 -> Master -> 2 slaves (both MariaDB 10.2). *CentOS 7
Most of my queries are prepared statements so the master basically handles 90% of the queries right now.
I've enabled the hintfilter and tried to add a hint to a query:
/* maxscale route to server server2 */
Unfortunately, it still ends up on the master.
I understood that MaxScale 2.2 should introduce some auto solution for prepared statements. However, I need some temp solution(I'll try to look into ProxySQL if none is found).
Any help would be highly appreciated.
If you used the mysql command line client to test it, remember to enable SQL comments by using the -c flag.
Since MaxScale 2.0.1, the hint mechanism will override any decisions taken by the router itself if the router supports hints. The readwritesplit and schemarouter routers are currently the only routers that support routing hints so make sure you are using one of these routers.
The following documentation link indicates that the docker driver needs to be configured on all compute nodes
from
compute_driver= libvirt.LibvirtDriber
to
compute_driver=docker.DockerDriver
Does this means there will not be an option to select the instantiation of a normal VM ? Will the horizon UI allow to select which type of virtualization ( docker vs kvm ) to be selected ?
In openstack you cannot have hybrid compute drivers unless they are separated by AZs. So it's either one or the other.
Of course the hackish work around would be to spin up an openstack compute instance inside of the docker / lxc environment and join it to a new az as a libvirt node....
a bit of inception there though, and it makes your scheduler basically worthless.
With the basic OpenStack you can't, but you can write and add a filter which makes it possible... Just write a class with a host_passes method and add your new filter to nova scheduler filters.
I did it and it works.