You've already forked node-redis
mirror of
https://github.com/redis/node-redis.git
synced 2025-08-09 00:22:08 +03:00
7d2629f083
* Support esModuleInterop set to false. When testing the upcoming 4.x release, we got a bunch of typescript errors emitted from this project. We quickly realized this is because the library uses the esModuleInterop flag. This makes some imports _slightly_ easier to write, but it comes at a cost: it forces any application or library using this library to *also* have esModuleInterop on. The `esModuleInterop` flag is a bit of a holdover from an earlier time, and I would not recommend using it in libraries. The main issue is that if it's set to true, you are forcing any users of the library to also have `esModuleInterop`, where if you keep have it set to `false` (the default), you leave the decision to the user. This change should have no rammifications to users with `esModuleInterop` on, but it will enable support for those that have it off. This is especially good for library authors such as myself, because I would also like to keep this flag off to not force *my* users into this feature. * All tests now pass! * Move @types/redis-parser into client sub-package and removed a comma
106 lines
3.1 KiB
TypeScript
106 lines
3.1 KiB
TypeScript
import { strict as assert } from 'assert';
|
|
import testUtils, { GLOBAL } from '../test-utils';
|
|
import { ClusterSlotStates } from '../commands/CLUSTER_SETSLOT';
|
|
import { SQUARE_SCRIPT } from '../client/index.spec';
|
|
|
|
// We need to use 'require', because it's not possible with Typescript to import
|
|
// function that are exported as 'module.exports = function`, without esModuleInterop
|
|
// set to true.
|
|
const calculateSlot = require('cluster-key-slot');
|
|
|
|
describe('Cluster', () => {
|
|
testUtils.testWithCluster('sendCommand', async cluster => {
|
|
await cluster.connect();
|
|
|
|
try {
|
|
await cluster.publish('channel', 'message');
|
|
await cluster.set('a', 'b');
|
|
await cluster.set('a{a}', 'bb');
|
|
await cluster.set('aa', 'bb');
|
|
await cluster.get('aa');
|
|
await cluster.get('aa');
|
|
await cluster.get('aa');
|
|
await cluster.get('aa');
|
|
} finally {
|
|
await cluster.disconnect();
|
|
}
|
|
}, GLOBAL.CLUSTERS.OPEN);
|
|
|
|
testUtils.testWithCluster('multi', async cluster => {
|
|
const key = 'key';
|
|
assert.deepEqual(
|
|
await cluster.multi()
|
|
.set(key, 'value')
|
|
.get(key)
|
|
.exec(),
|
|
['OK', 'value']
|
|
);
|
|
}, GLOBAL.CLUSTERS.OPEN);
|
|
|
|
testUtils.testWithCluster('scripts', async cluster => {
|
|
assert.equal(
|
|
await cluster.square(2),
|
|
4
|
|
);
|
|
}, {
|
|
...GLOBAL.CLUSTERS.OPEN,
|
|
clusterConfiguration: {
|
|
scripts: {
|
|
square: SQUARE_SCRIPT
|
|
}
|
|
}
|
|
});
|
|
|
|
testUtils.testWithCluster('should handle live resharding', async cluster => {
|
|
const key = 'key',
|
|
value = 'value';
|
|
await cluster.set(key, value);
|
|
|
|
const slot = calculateSlot(key),
|
|
source = cluster.getSlotMaster(slot),
|
|
destination = cluster.getMasters().find(node => node.id !== source.id)!;
|
|
|
|
await Promise.all([
|
|
source.client.clusterSetSlot(slot, ClusterSlotStates.MIGRATING, destination.id),
|
|
destination.client.clusterSetSlot(slot, ClusterSlotStates.IMPORTING, destination.id)
|
|
]);
|
|
|
|
// should be able to get the key from the source node using "ASKING"
|
|
assert.equal(
|
|
await cluster.get(key),
|
|
value
|
|
);
|
|
|
|
await Promise.all([
|
|
source.client.migrate(
|
|
'127.0.0.1',
|
|
(<any>destination.client.options).socket.port,
|
|
key,
|
|
0,
|
|
10
|
|
)
|
|
]);
|
|
|
|
// should be able to get the key from the destination node using the "ASKING" command
|
|
assert.equal(
|
|
await cluster.get(key),
|
|
value
|
|
);
|
|
|
|
await Promise.all(
|
|
cluster.getMasters().map(({ client }) => {
|
|
return client.clusterSetSlot(slot, ClusterSlotStates.NODE, destination.id);
|
|
})
|
|
);
|
|
|
|
// should handle "MOVED" errors
|
|
assert.equal(
|
|
await cluster.get(key),
|
|
value
|
|
);
|
|
}, {
|
|
serverArguments: [],
|
|
numberOfNodes: 2
|
|
});
|
|
});
|